-
Notifications
You must be signed in to change notification settings - Fork 22
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
Issue #2349: Portfolio templates - [RJM] #2431
Conversation
🥳 Successfully deployed to developer sandbox rjm. |
🥳 Successfully deployed to developer sandbox rjm. |
🥳 Successfully deployed to developer sandbox rjm. |
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.
Ok - this took a while to read through, but so far the work looks solid.
I do recommend adding comments in our scss overrides, as it is not clear why some of them exist and what they affect. I totally appreciate the organization into separate files (frontend architecture can get spaghetti in a hurry without some housekeeping).
I also really like the new approach with our context for flags. Seems like a good standard overall for waffle flag items.
I plan on doing testing on RJM tomorrow to verify no breakages. But overall, no issues with the code (except a desire for more comments)
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 a few things. Nice refactor work here
Approved ^^. Just remember to look over some of the comments + implement, particularly this one: Won't block the review on it, but I'll take a look after you answer! |
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.
A few things:
|
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.
(see comment)
🥳 Successfully deployed to developer sandbox rjm. |
I'll try merging main then pushing, and will check Figma again when I get a chance Edit: 1 and 2 should be fixed |
Fixed |
🥳 Successfully deployed to developer sandbox rjm. |
🥳 Successfully deployed to developer sandbox rjm. |
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.
Nice work but see @CocoByte s suggestions, too
> .usa-navbar { | ||
// This is a dangerous override to USWDS, necessary because we have a tooltip on the logo | ||
overflow: visible; | ||
} |
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.
(nitpick/optional) Couldn't we this behaviour to a class on the same element that usa-navbar resides in?
user_portfolios = Portfolio.objects.filter(creator=request.user) | ||
first_portfolio = user_portfolios.first() |
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.
user_portfolios = Portfolio.objects.filter(creator=request.user) | |
first_portfolio = user_portfolios.first() | |
first_portfolio = Portfolio.objects.filter(creator=request.user).first() |
(Optional) you could also combine this field if you want. Optional though
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 (just needs linting)
Hi Rachid, adding some feedback after a first pass for visual and AC. This is looking so great!
|
🥳 Successfully deployed to developer sandbox rjm. |
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.
Looks great!
Ticket
Resolves #2349
Changes
Context for reviewers
Devs: Follow the org_user_status global context and logo_clickable view context to understand how the different contexts are managed.
Designers: The suborg display still follows the original design. We can revise when we get to org group UI implementation or filter refactoring.
The nav on mobile uses out of the box styles and colors for both portfolio and regular users.
All: You may need to look at the old profile stuff and make sure it still works as expected as I've refactored how we're doing a context that profile uses - @zandercymatics
Setup
Add a portfolio with you as creator, makes sure the waffle flag is turned on.
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
Ensured code standards are met (Code reviewer)
Validated user-facing changes as a developer
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)
Tested with multiple browsers, the suggestion is to use ones that the developer didn't (check off which ones were used)
(Rarely needed) Tested as both an analyst and applicant user
Note: Multiple code reviewers can share the checklists above, a second reviewers should not make a duplicate checklist
As a designer reviewer, I have
Verified that the changes match the design intention
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)
(Rarely needed) Tested as both an analyst and applicant user
Screenshots