-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for ViewComponent v3 #277
Comments
Hey @Spone, Yeah, we plan to upgrade. The codemod for slots looks very useful. I will try it out when I'll be working on upgrade 👍 |
@Spone I just used it during the upgrade to ViewCompoent v3 and it was extremely useful. We had only 3 false positive warnings on our codebase:
All of them are custom methods that start from the same name as a slot. It would be very helpful to see this as a part of ViewComponent. Thanks for your work on this ❤️ |
@Spone until https://github.com/ViewComponent/view_component/pull/1669/files is not merged would you mind if I include this codemod to our gem as a rake task? This will help to upgrade apps that are relying on our library |
@kirillplatonov I have a counteroffer 😀 work with me to get the PR past the finish line and get it merged in VC! |
@Spone I'm in 🙌 |
I'll get in touch with you next week! |
Hello! I'd like to know if you're planning on supporting ViewComponent v3. There are currently two release candidates (v3.0.0.rc1 and v3.0.0.rc2) that you can try out.
I think the deprecation slots setter methods will generate the most work (you have to use
with_SLOT_NAME
instead).I'm currently exploring the idea of providing a linter/codemod to help with this: ViewComponent/view_component#1669
Would you be interested in trying it out and providing feedback?
The text was updated successfully, but these errors were encountered: