-
Notifications
You must be signed in to change notification settings - Fork 66
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
Move Decision Review code to Engine - spike #19549
Conversation
Error: A file (or its parent directories) was deleted but its reference still exists in CODEOWNERS. Please update the .github/CODEOWNERS file and delete the entry for the Offending file: app/controllers/v1/decision_review_notification_callbacks_controller.rb |
Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: modules/decision_reviews/Gemfile |
Generated by 🚫 Danger |
...ews/app/controllers/decision_reviews/v1/decision_review_notification_callbacks_controller.rb
Dismissed
Show dismissed
Hide dismissed
- one controller with tests duplicated
- keep controllers duplicated for now
79271ea
to
aa25ac2
Compare
Spike complete, starting feature work on new branch, closing this PR |
Summary
Move some Decision Review controllers and Sidekiq jobs into a new engine in the modules folder. Spike to help team decide if we want to pursue full code isolation.
Decision Reviews, yes
No flipper, no changes to behavior just refactoring. Initial plan is to keep routes and controllers in main app and engine while we test the transition.
Related issue(s)
department-of-veterans-affairs/va.gov-team#97410
Testing done
Code was not contained in an engine
Check the new engine endpoints behave the same way as existing endpoints
What areas of the site does it impact?
DR endpoints and background jobs
Acceptance criteria