-
Notifications
You must be signed in to change notification settings - Fork 21
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
#3402: Portfolio and domain invitation updates [HOTGOV] #3428
base: main
Are you sure you want to change the base?
Conversation
🥳 Successfully deployed to developer sandbox hotgov. |
src/registrar/admin.py
Outdated
has_errors = any(message.level_tag in ["error", "warning"] for message in storage) | ||
has_errors = any(message.level_tag in ["error"] for message in storage) |
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.
errors are blocking and warnings are not, so need to be handled differently
messages.warning(request, str(exception)) | ||
messages.error(request, str(exception)) | ||
elif isinstance(exception, AlreadyDomainInvitedError): | ||
messages.warning(request, str(exception)) | ||
messages.error(request, str(exception)) | ||
elif isinstance(exception, IntegrityError): | ||
messages.warning(request, f"{email} is already a manager for this domain") | ||
messages.error(request, f"{email} is already a manager for this domain") | ||
else: | ||
logger.warning("Could not send email invitation (Other Exception)", exc_info=True) | ||
messages.warning(request, "Could not send email invitation.") | ||
messages.error(request, "Could not send email invitation.") |
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.
errors that block functions are errors, warning that allow functionality to continue are warnings
🥳 Successfully deployed to developer sandbox hotgov. |
🥳 Successfully deployed to developer sandbox hotgov. |
🥳 Successfully deployed to developer sandbox hotgov. |
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 - tested and verified on hotgov
🥳 Successfully deployed to developer sandbox hotgov. |
🥳 Successfully deployed to developer sandbox hotgov. |
Ticket
Resolves #3402
Resolves #3378
Resolves #3401
Resolves #3403
Changes
Context for reviewers
Setup
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
Validated user-facing changes as a developer
Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.
As a designer reviewer, I have
Verified that the changes match the design intention
Validated user-facing changes as a designer
References
Screenshots