Skip to content

feat(authz): tighten title layout spacing and shrink the header action buttons - #249

Merged
jacobo-dominguez-wgu merged 1 commit into
masterfrom
jacobo/title-layout
Oct 7, 2026
Merged

jacobo-dominguez-wgu merged 1 commit into
masterfrom
jacobo/title-layout

Conversation

@jacobo-dominguez-wgu

@jacobo-dominguez-wgu jacobo-dominguez-wgu commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Description

AuthZTitle previously rendered a Breadcrumb unconditionally, so pages with no navigation context (no activeLabel and no navLinks) still showed an empty, orphaned breadcrumb. This PR renders the breadcrumb only when there is something to show, and tightens the header band spacing and action-button sizing.

Supporting information

Fixes #238
Figma https://www.figma.com/design/xnmQJq1cTRVqNrs31R8zDM/AuthZ---v2?node-id=40000174-2&p=f&t=AvQgCUER8u7BJBiE-0

Testing instructions

  1. Check out this branch and run the app (or the authz module).
  2. Open a page that renders AuthZTitle without an activeLabel or navLinks (e.g. the AuthZ home) and confirm no breadcrumb is shown.
  3. Open a page that passes navLinks and/or an activeLabel (e.g. the audit user page) and confirm the breadcrumb still renders with the correct links and active label.
  4. Confirm the header band spacing is tighter and the action buttons (including "Assign role") render at the small size.
  5. Run the unit tests: npx jest src/authz-module/components/AuthZTitle.test.tsx — all tests pass, including does not render the breadcrumb when there is no activeLabel and no navLinks.

Other information

image image

@openedx-webhooks

Copy link
Copy Markdown

Thanks for the pull request, @jacobo-dominguez-wgu!

This repository is currently maintained by @openedx/committers-frontend.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Oct 5, 2026
@codecov

codecov Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.71%. Comparing base (fee5557) to head (a5ce29a).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #249      +/-   ##
==========================================
+ Coverage   98.53%   98.71%   +0.17%     
==========================================
  Files          73       80       +7     
  Lines        1299     1396      +97     
  Branches      426      468      +42     
==========================================
+ Hits         1280     1378      +98     
+ Misses         19       18       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dcoa dcoa left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It matches the Figma. However I have a question:

The PR description says:

tightens the header band spacing and action-button sizing for visual consistency

For me is not clear, what is the reference I need to validate to ensure the UI is consistent?

For example, reducing the spacing in the header is not consistent if I compare with other applications titles such as Account or Catalog.

Comment thread .github/pull_request_template.md Outdated
Comment thread src/authz-module/components/AuthZTitle.tsx Outdated
Comment thread src/authz-module/components/AuthZTitle.tsx Outdated
@jacobo-dominguez-wgu

Copy link
Copy Markdown
Contributor Author

It matches the Figma. However I have a question:
The PR description says:

tightens the header band spacing and action-button sizing for visual consistency

For me is not clear, what is the reference I need to validate to ensure the UI is consistent?

For example, reducing the spacing in the header is not consistent if I compare with other applications titles such as Account or Catalog.

Thanks, I have applied your suggestions. The intention was to keep consistency with studio home button sizes, but I have updated the description to reduce noise.

@carlos-marquez-wgu carlos-marquez-wgu left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Tested locally and it works as the testing instructions says, matches figma, and unit tests also passes, thanks!

Image Image

@dcoa dcoa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I will leave my approve, so you can merge early. But please take in consideration the following nits

size="sm"
iconBefore={Plus}
onClick={handleClick}
className="font-weight-light"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this was added when you updated the PR but this is not needed, the Figma shows font-weight: 400 that is the default of paragon button class

Suggested change
className="font-weight-light"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Applied.

<Row className="mt-4">
<Col xs={12} md={7} className="mb-4">
<div className="d-flex align-items-center flex-column-sm">
<div className="page-band py-3 bg-light-100">

@dcoa dcoa Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I was just reviewing the Figma and noticed that this area has a height of 86px, but the current one gives a total of 72px so:

Suggested change
<div className="page-band py-3 bg-light-100">
<div className="page-band py-4 bg-light-100">

It will result in 88px that is closer to the Figma value.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Applied

@jacobo-dominguez-wgu
jacobo-dominguez-wgu merged commit fccbc43 into master Oct 7, 2026
6 checks passed
@jacobo-dominguez-wgu
jacobo-dominguez-wgu deleted the jacobo/title-layout branch October 7, 2026 16:23
@openedx-semantic-release-bot

Copy link
Copy Markdown
Collaborator

🎉 This PR is included in version 1.0.0-alpha.7 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U released on @latest

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

AuthZ layout title: reduce title spacing + shrink Assign role button

5 participants