Skip to content
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

#2969 - Domains and request table needs visual header - [NL] #3294

Merged
merged 12 commits into from
Jan 11, 2025

Conversation

CocoByte
Copy link
Contributor

@CocoByte CocoByte commented Jan 3, 2025

Ticket 2969

Resolves #2969

Changes

  • In domain request table javascript, combined delete column with action column
  • Made "Action" header text visible
  • Force columns of Domain and Domain Request tables in non-org views to align

Context for reviewers

Setup

Ensure org model waffle flags are disabled

Code Review Verification Steps

Go to the Domain and Domain Request table view. Verify that...

  • "Action" appears in the table header for the last column of both tables
  • the ANDI output for the "Action" header is "Action"
  • The delete button appears under the "Action" column instead of its own column
  • The column widths of the Domain and Domain Request table are aligned

As the original developer, I have

Satisfied acceptance criteria and met development standards

  • Met the acceptance criteria, or will meet them in a subsequent PR
  • Created/modified automated tests
  • Update documentation in READMEs and/or onboarding guide

Ensured code standards are met (Original Developer)

  • If any updated dependencies on Pipfile, also update dependencies in requirements.txt.
  • Interactions with external systems are wrapped in try/except
  • Error handling exists for unusual or missing values

Validated user-facing changes (if applicable)

  • Tag @dotgov-designers in this PR's Reviewers for design review. If code is not user-facing, delete design reviewer checklist
  • Verify new pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
  • Checked keyboard navigability
  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

  • Pulled this branch locally and tested it
  • Verified code meets all checks above. Address any checks that are not satisfied
  • Reviewed this code and left comments. Indicate if comments must be addressed before code is merged
  • Checked that all code is adequately covered by tests
  • Verify migrations are valid and do not conflict with existing migrations

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.

  • New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
  • Checked keyboard navigability
  • Meets all designs and user flows provided by design/product
  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
  • (Rarely needed) Tested as both an analyst and applicant user

As a designer reviewer, I have

Verified that the changes match the design intention

  • Checked that the design translated visually
  • Checked behavior. Comment any found issues or broken flows.
  • Checked different states (empty, one, some, error)
  • Checked for landmarks, page heading structure, and links

Validated user-facing changes as a designer

  • Checked keyboard navigability
  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
  • Tested with multiple browsers (check off which ones were used)
    • Chrome
    • Microsoft Edge
    • FireFox
    • Safari
  • (Rarely needed) Tested as both an analyst and applicant user

References

Screenshots

@CocoByte CocoByte requested a review from abroddrick as a code owner January 3, 2025 19:50
Copy link

github-actions bot commented Jan 3, 2025

🥳 Successfully deployed to developer sandbox nl.

@CocoByte CocoByte changed the title [DRAFT] Action column #2969 - Domains and request table needs visual header Jan 3, 2025
@CocoByte CocoByte changed the title #2969 - Domains and request table needs visual header #2969 - Domains and request table needs visual header - [NL] Jan 6, 2025
Copy link

github-actions bot commented Jan 6, 2025

🥳 Successfully deployed to developer sandbox nl.

Copy link

github-actions bot commented Jan 7, 2025

🥳 Successfully deployed to developer sandbox nl.

Copy link

github-actions bot commented Jan 8, 2025

🥳 Successfully deployed to developer sandbox nl.

Copy link

github-actions bot commented Jan 8, 2025

🥳 Successfully deployed to developer sandbox nl.

Copy link

github-actions bot commented Jan 8, 2025

🥳 Successfully deployed to developer sandbox nl.

Copy link

github-actions bot commented Jan 8, 2025

🥳 Successfully deployed to developer sandbox nl.

Copy link

github-actions bot commented Jan 9, 2025

🥳 Successfully deployed to developer sandbox nl.

@rachidatecs rachidatecs self-assigned this Jan 10, 2025
Copy link
Contributor

@rachidatecs rachidatecs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dave brings up a good point. Revise the var name again (my suggestion was not great), remove a couple of obsolete comments and good to merge.

@@ -214,7 +214,7 @@ <h2>Status</h2>
scope="col"
role="columnheader"
>
<span class="usa-sr-only">Action</span>
Action
</th>
</tr>
</thead>
Copy link
Contributor

@rachidatecs rachidatecs Jan 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the comment below: <!-- AJAX will populate this tbody -->

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this comment is still valid. We want to indicate that AJAX builds the table body

@@ -186,7 +186,7 @@ <h2>Status</h2>
<th data-sortable="creator" scope="col" role="columnheader">Created by</th>
{% endif %}
<th data-sortable="status" scope="col" role="columnheader">Status</th>
<th scope="col" role="columnheader"><span class="usa-sr-only">Action</span></th>
<th scope="col" role="columnheader">Action</th>
<!-- AJAX will conditionally add a th for delete actions -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this comment

Copy link

🥳 Successfully deployed to developer sandbox nl.

@CocoByte CocoByte merged commit 3c91ea4 into main Jan 11, 2025
10 checks passed
@CocoByte CocoByte deleted the nl/2969-visual-table-headers branch January 11, 2025 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Domains and request table needs visual header
3 participants