-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Not clear how to avoid the relative_url_root
deprecation message
#399
Comments
This is not a bug. We will remove Does this deprecation message cause any issues in your project? Regarding changelog, we have a dedicated entry for this depreciation. Line 26 in eb6c420
I think your suggestion to show the direction message only if it is set is good. |
Thanks for the prompt answer!
I do agree. I was not sure this was a feature request either, and I was even thinking to open a discussion, but in the end I decided to use the bug template the same, apologies for the confusion
I can confirm this works, diowa/ruby3-rails7-bootstrap-heroku@e03ee10 Thanks again and Happy New Year! |
Thanks for reporting the issue |
@tagliala |
Shakapacker 7.2.0 deprecated
relative_url_root
, but is not clear from changelog, the documentation, or a freshly generated config how to avoid this warning.I'm not sure what
relative_url_root
is used for, but probably shakapacker should print the deprecation error only if it is being used (have a value different fromblank
?)Expected behavior:
Have an option/documentation/config entry to avoid the deprecated behavior
Actual behavior:
Running specs logs a warning on the console.
Small, reproducible repo:
diowa/ruby3-rails7-bootstrap-heroku#702
https://github.com/diowa/ruby3-rails7-bootstrap-heroku/actions/runs/7364428208/job/20044793977#step:8:14
Setup environment:
The text was updated successfully, but these errors were encountered: