-
Notifications
You must be signed in to change notification settings - Fork 19
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
#2591: Remove profile feature flag - [MEOWARD] #2738
Conversation
🥳 Successfully deployed to developer sandbox meoward. |
🥳 Successfully deployed to developer sandbox meoward. |
1 similar comment
🥳 Successfully deployed to developer sandbox meoward. |
🥳 Successfully deployed to developer sandbox meoward. |
🥳 Successfully deployed to developer sandbox meoward. |
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.
Hi! Maybe I jumped the gun on reviewing this, but it looks like there are a number of failing tests still. If this is still under construction, mind adding "[DRAFT]" to front of the PR title?
… meoward/2591-Remove-Profile-feature-flag
🥳 Successfully deployed to developer sandbox meoward. |
changes addresses, tests passing
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.
src/registrar/admin.py
Outdated
recipient = obj.creator | ||
else: | ||
recipient = None | ||
# TODO 2574: remove lines 1977-1978 (refactor as needed) |
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.
Still need this todo?
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.
I can remove!
@@ -15,7 +15,7 @@ | |||
</svg> | |||
{% endif %} | |||
{% endif %} | |||
<a href="{% namespaced_url 'domain-request' this_step %}" | |||
<a href="{% namespaced_url 'domain-request' this_step %}" |
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.
seems like this file was accidentally included? I'm in favor of keeping this though as its some cleanup stuff
@@ -39,4 +39,4 @@ | |||
{% endfor %} | |||
</ul> | |||
</nav> | |||
</div> | |||
</div> |
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.
I'd say though just remember to end the file with a newline. I think thats our convention typically
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.
updated
src/registrar/tests/test_views.py
Outdated
senior_official=contact_user, | ||
) | ||
def test_domain_your_contact_information_when_profile_feature_on(self): | ||
"""test that Your contact information is not accessible when profile feature is on""" | ||
with override_flag("profile_feature", active=True): |
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 like you missed a reference to profile_feature! I think for this test though you can actually delete it - we won't need it anymore
home_page = self.app.get(reverse("user-profile")) | ||
self.assertContains(home_page, self.domain.name) |
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.
(Blocking) why was this changed? We shouldn't see the domain name on user-profile
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.
When a new user first logs in, they are taken to the user-profile
page, instead of the home
.
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.
@asaki222 I see your point regarding testing that! However, this test is supposed to test on if a domain invite adds that domain to the domain table after the user logs in. They only see this profile page when they are missing information on the user object - which would be why you are seeing that behavior
Since the purpose of this test is different, can you revert this? You will need to just add more data to the user object defined on 755. I think title and phone, but maybe one additional field. This will cause the user to redirect to home
The only weird thing about this is why the test is passing at all - basically I don't think the domain name should exist on the user profile page. Looking at it now, this is actually a bug caused by line 739 - the email address has the name of the domain!
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.
Regarding that error with the test - do you mind adding a line like self.assertNotContains(home_page, email_address)
as well?
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.
@zandercymatics if I revert this test, and added the
self.assertNotContains(home_page, email_address)
, it would fail since its technically on the home page. Is that what you meant?
🥳 Successfully deployed to developer sandbox meoward. |
Removed @zandercymatics , I must have missed these when I was trying to debug |
🥳 Successfully deployed to developer sandbox meoward. |
1 similar comment
🥳 Successfully deployed to developer sandbox meoward. |
🥳 Successfully deployed to developer sandbox meoward. |
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.
Your changes look great! I ran it locally and it works on meoward!
Just two more things:
- There are some old documentation artifacts for profile_feature in
adding-feature-flags.md
and on the function description forwaffle_flag.py
. Can you remove those? - There is a blocking change on that test_domain_invitation flow one! I left some more details as to why - its a pretty subtle one
🥳 Successfully deployed to developer sandbox meoward. |
🥳 Successfully deployed to developer sandbox meoward. |
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.
your changes look good but I think you need to lint. The jobs haven't passed yet - but if all of them do then all is good. You just need to also remove the references in our documentation, then I will approve after both of those are true!
🥳 Successfully deployed to developer sandbox meoward. |
🥳 Successfully deployed to developer sandbox meoward. |
1 similar comment
🥳 Successfully deployed to developer sandbox meoward. |
Ticket
Resolves #2591
Changes
Context for reviewers
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