-
Notifications
You must be signed in to change notification settings - Fork 434
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
Coexistence issues with active_scaffold
gem
#2032
Comments
@juankiz thank you for the report I don't know exactly what may have caused this and how to fix it, but if I have some time to investigate this I will let you know what I find Also @joelhawksley @camertron what do you think |
@juankiz I'd love for us to find a way for ViewComponent to not conflict with |
Hey @joelhawksley, long time no see. I hope all is well. I just stumbled upon this bug too. I'm looking to dump ActiveScaffold, so will just do that before I introduce ViewComponents. Just chiming in as a second example. |
Oh hey @planetmcd! I still say Thanks for the corroborating report ❤ |
Love that. Thanks for spearheading this library! |
My best guess is that something similar to either this issue or this issue that is clashing with this file on active_scaffold but since I'm using rails 7.0 I cant use the
render_component
method.I would stick to just add the
render_component
method back directly on my application code, but since it'll be removed in the future, I'm not sure what's the best way to move forward with this.Steps to reproduce
On a working Rails + ViewComponent app, add the
active_scaffold
gem.You can view a minimal example on this repo
Expected behavior
Actual behavior
An exception is thown:
Backtrace:
System configuration
Rails version:
7.0.8.3
Ruby version:
3.3.1
Gem version:
3.12.1
The text was updated successfully, but these errors were encountered: