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

Empty <Partner> Stamps category appears when user is not on AllowList #2884

Closed
erichfi opened this issue Sep 19, 2024 · 1 comment · Fixed by #2888
Closed

Empty <Partner> Stamps category appears when user is not on AllowList #2884

erichfi opened this issue Sep 19, 2024 · 1 comment · Fixed by #2888
Assignees

Comments

@erichfi
Copy link
Collaborator

erichfi commented Sep 19, 2024

Overview
When a partner has an AllowList (and no other custom stamp), users who are not on the AllowList still see an empty <Partner> Stamps category. This behavior causes confusion, as the section appears without content.

Steps To Reproduce

  1. Go to the <Partner> dashboard.
  2. Ensure you are not on the AllowList for this partner.
  3. Click on the "Stamps" section in the profile.
  4. Scroll down to view the <Partner> Stamps category.

Observed behavior
The <Partner> Stamps category appears, but it is empty because the user is not on the AllowList and there are no other custom stamps.

Expected behavior
The <Partner> Stamps category should be hidden entirely if the user is not on the AllowList and no other stamps are available for this partner.

Screenshots
N/A (can be added if necessary)

Additional context
N/A

@erichfi erichfi converted this from a draft issue Sep 19, 2024
@lucianHymer lucianHymer self-assigned this Sep 19, 2024
@erichfi erichfi moved this from Product/UX Review to Ready to Deploy in Passport New Sep 24, 2024
@erichfi erichfi moved this from Ready to Deploy to Done in Passport New Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants
@lucianHymer @erichfi and others