-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
File cleanup/organization in controllers/concerns
#27846
Conversation
This pull request has merge conflicts that must be resolved before it can be merged. |
8f86f6c
to
d9d3f75
Compare
This pull request has resolved merge conflicts and is ready for review. |
d9d3f75
to
bd82ea7
Compare
bd82ea7
to
a59526c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #27846 +/- ##
=======================================
Coverage 82.67% 82.67%
=======================================
Files 1030 1030
Lines 28145 28145
Branches 4549 4549
=======================================
Hits 23270 23270
Misses 3788 3788
Partials 1087 1087 ☔ View full report in Codecov by Sentry. |
I noticed a few of the controller concerns were only used in the API area, and was going to move them into an
Api::
namespace. Once I started that I noticed a similar dynamic with someSettings::
andAuth::
andAdmin::
concerns as well.This is just a file/module move to stop
concerns
from becoming junk drawer; should not be behavior change.There may be room for similar org/cleanup in the models concerns, since many of those are only used in one spot. Will do that next if we like this.