-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Change namespace of Active Storage rake task #30280
Change namespace of Active Storage rake task #30280
Conversation
r? @matthewd (@rails-bot has picked a reviewer for you, use r? to override) |
This feels to me like the sort of place we might deliberately choose the no-underscore spelling. They should be consistent... I just wonder which one we'd rather standardize on. @dhh? |
This problem should be going away shortly as the rake task is getting nixed in favor of a better way to install this migration. In general, I don't think these tasks should be prefixed by their framework. It's db:create, not active_record:db:create. And even if we did keep this rake task, it should be something like blob:migrations. |
Yeah, I was thinking that ASt rake tasks could just be under By the way, I think the correct fix might actually be making |
Ah, I agree with |
Thank you for discussion. I'd like to open a new PR with the following changes.
What do you think? |
I opened a PR #30378 so that it would proceed on a code base. |
@dhh I got it. Thank you for sharing your information with me. |
Summary
The following is a display of the result of
rake -T
using the Active Storage application.The namespace of
active_storage:install:migrations
andactivestorage:install
are different. This PR unifies the namespace of Active Storage rake task toactive_storage
.The namespace of
active_storage:install:migrations
depends onEngine#railtie_name
.rails/railties/lib/rails/engine.rb
Lines 627 to 630 in 0789d09
So I think that the change target is namespace defined by activestorage.rake.