-
Notifications
You must be signed in to change notification settings - Fork 62
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
Rails 6 Zeitwerk Warning #27
Comments
Thanks for alerting me to this. I've been working on a new version of this gem that's compatible with Rails 6 and will incorporate this feedback into those changes. |
I'm seeing this warning as well. Any progress on Rails 6 compatibility? |
@aidandamerell @moveson I'm curious where you both are seeing this. In the Rails log? I'm running the gem on a freshly created Rails 6.1 project (with Devise) and I'm not seeing these warnings in the log, at least not in development mode. If you can provide more detail I'd like to help. |
Hey, I seem to be in the same boat although my error only includes This is a rails 6.0 app that is being bumped to 6.1. Will keep poking around to see if I can figure out what is going on. Curious if @aidandamerell or @moveson made progress?
In a completely unscientific experiment the following seems to remove the error:
|
Are you still getting this warning? It shouldn't be happening any longer. |
DEPRECATION WARNING: Initialization autoloaded the constants ActionText::ContentHelper and ActionText::TagHelper.
Being able to do this is deprecated. Autoloading during initialization is going
to be an error condition in future versions of Rails.
Reloading does not reboot the application, and therefore code executed during
initialization does not run again. So, if you reload ActionText::ContentHelper, for example,
the expected changes won't be reflected in that stale Module object.
These autoloaded constants have been unloaded.
Please, check the "Autoloading and Reloading Constants" guide for solutions.
(called from <top (required)> at XXX
The text was updated successfully, but these errors were encountered: