-
Notifications
You must be signed in to change notification settings - Fork 72
Feature/add mass store mass update to all api controllers #1779
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
base: dev
Are you sure you want to change the base?
Feature/add mass store mass update to all api controllers #1779
Conversation
…e/add-mass-store-mass-update-to-all-api-controllers
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Tip 📝 Customizable high-level summaries are now available in beta!You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.
Example instruction:
Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
I reviewed the controller implementation, and I think we can avoid repeating the same logic across all API resources by introducing a shared Proposed alternative:
|
This PR extends the work introduced in PR #1771, which added
massStoreandmassUpdatesupport for the Activity API.I’ve applied the same pattern to all API controllers, following a consistent and predictable structure:
MassStore<Model>RequestandMassUpdate<Model>Requestgenerated for every resourceStore<Model>Request/Update<Model>Request$request->input(...))<model>_create/<model>_edit)Mercator\Core\Models\I have not been able to run full tests yet, as I believe the new global model namespace refactor is not fully implemented across the project (please correct me if I’m wrong).
Happy to adjust anything needed.
Open to any feedback or required modifications.