-
Notifications
You must be signed in to change notification settings - Fork 25
#3181 - dynamic labels for investigator and senior official [-Bob] #3577
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
#3181 - dynamic labels for investigator and senior official [-Bob] #3577
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just needs some cleanup, but everything is here! I like how you are addressing this holistically, which is a very nice touch
src/registrar/templates/django/admin/includes/detail_table_fieldset.html
Outdated
Show resolved
Hide resolved
src/registrar/templates/django/admin/includes/detail_table_fieldset.html
Outdated
Show resolved
Hide resolved
Co-authored-by: zandercymatics <[email protected]>
🥳 Successfully deployed to developer sandbox nl. |
🥳 Successfully deployed to developer sandbox nl. |
🥳 Successfully deployed to developer sandbox nl. |
Note for @zandercymatics and @CocoByte, I only did a skim on this one |
…and-senior-official' into nl/3181-labels-for-investigator-and-senior-official
🥳 Successfully deployed to developer sandbox nl. |
🥳 Successfully deployed to developer sandbox nl. |
🥳 Successfully deployed to developer sandbox nl. |
🥳 Successfully deployed to developer sandbox nl. |
🥳 Successfully deployed to developer sandbox nl. |
Fyi - I pushed latest of this branch to bob! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The senior official field isn't a select2 field on domain request for some reason so your function doesn't apply here! This actually should be one (as it was one, not sure what happened).
All you need to do to add it is to add it to the autocomplete_fields
array. Double check the javascript for this field once you do this though, let me know if you run into any errors and I can assist there.
src/registrar/templates/django/admin/includes/detail_table_fieldset.html
Outdated
Show resolved
Hide resolved
Co-authored-by: zandercymatics <[email protected]>
…ldset.html Co-authored-by: zandercymatics <[email protected]>
🥳 Successfully deployed to developer sandbox nl. |
1 similar comment
🥳 Successfully deployed to developer sandbox nl. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
🥳 Successfully deployed to developer sandbox nl. |
Ticket 3181
Resolves #3181
Changes
Context for reviewers
The two dropdowns listed in the original ACs really just highlight a more systemic issue with our ARIA labels for select2 dropdowns. The updates for this ticket addresses all select2 components throughout Django Admin so they will all follow the same pattern.
Setup
Code Review Verification Steps
As the original developer, I have
Satisfied acceptance criteria and met development standards
Ensured code standards are met (Original Developer)
Validated user-facing changes (if applicable)
As a code reviewer, I have
Reviewed, tested, and left feedback about the changes
Validated user-facing changes as a developer
Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.
As a designer reviewer, I have
Verified that the changes match the design intention
Validated user-facing changes as a designer
References
Screenshots