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

feat(issue-details): Display the resolution/archival reason on new UI #83555

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

leeandher
Copy link
Member

@leeandher leeandher commented Jan 15, 2025

Though the activity was still present, we stopped showing a banner for reasons associated with a resolution or archival. Those are brought back now alongside the new banner.

image image

@leeandher leeandher requested a review from a team as a code owner January 15, 2025 23:29
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jan 15, 2025
Copy link

codecov bot commented Jan 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #83555      +/-   ##
==========================================
- Coverage   87.53%   87.53%   -0.01%     
==========================================
  Files        9406     9406              
  Lines      537407   537384      -23     
  Branches    21163    21157       -6     
==========================================
- Hits       470397   470376      -21     
+ Misses      66664    66662       -2     
  Partials      346      346              

export function renderResolutionReason({
statusDetails,
project,
organization,
Copy link
Member

Choose a reason for hiding this comment

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

is there a reason we can't use useOrganization here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Didn't think it was worth refactoring the whole thing to be a hook. I'd have to look at the logic as well to ensure calling useRenderResolutionReason wouldn't cause issues if the issue wasn't resolved since hooks always need to be called and all that.

Passing a new prop skips all that

Copy link

codecov bot commented Jan 16, 2025

Bundle Report

Changes will increase total bundle size by 43.96kB (0.14%) ⬆️. This is within the configured threshold ✅

Detailed changes
Bundle name Size Change
app-webpack-bundle-array-push 31.3MB 43.96kB (0.14%) ⬆️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants