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

MPP-3636: Add type hints to Profile.fxa, handle null cases #4342

Merged
merged 2 commits into from
Jan 22, 2024

Conversation

jwhitlock
Copy link
Member

This PR is split from PR #4320.

The Profile.fxa property can return None if an account does not have a related Mozilla account. This PR adds the proper type hints, and update the calling code to handle the cases where Profile.fxa returns None.

It also updates tests to us a UUID for fake FxA IDs, rather than a 100-character random string.

How to test:

  • [ ] l10n changes have been submitted to the l10n repository, if any.
  • I've added a unit test to test for potential regressions of this bug.
  • [ ] I've added or updated relevant docs in the docs/ directory.
  • [ ] All UI revisions follow the coding standards, and use Protocol tokens where applicable (see /frontend/src/styles/tokens.scss).
  • Commits in this PR are minimal and have descriptive commit messages.

@jwhitlock jwhitlock requested a review from groovecoder January 22, 2024 16:54
@groovecoder groovecoder added this pull request to the merge queue Jan 22, 2024
Merged via the queue into main with commit cb9b82f Jan 22, 2024
25 checks passed
@groovecoder groovecoder deleted the profile-fxa-type-hint-mpp-3636 branch January 22, 2024 23:12
Copy link

sentry-io bot commented Feb 3, 2024

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

  • ‼️ OperationalError: the connection is closed /api/v1/relayaddresses/ View Issue

Did you find this useful? React with a 👍 or 👎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants