DBEX: assign toxic exposure submit endpoint & metadata #16802
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
NO:disability_526_toxic_exposure
includeToxicExposure
metadata attribute for a newly created in progress form, to be utilized on the frontend in tracking and reporting the inclusion of the toxic exposure section for the formsubmit_endpoint
attribute is set to'claims_api'
(implemented in previous PR update) is handled similarly to that of a user whosedisability_compensation_lighthouse_submit_migration
Flipper is enabledoptions
argument based ondisability_526_toxic_exposure
Flipper state for the current user, determining ultimate Lighthouse API submit endpoint ('/526'
or'/526/generatePDF'
)Related issue(s)
Testing done
What areas of the site does it impact?
Acceptance criteria