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

When an odk token expires is None, deactivate and replace #2583

Merged
merged 1 commit into from
Apr 12, 2024

Conversation

FrankApiyo
Copy link
Member

@FrankApiyo FrankApiyo commented Apr 11, 2024

Changes / Features implemented

Fix NoneType error

Steps taken to verify this change does what is intended

Added a test case

Side effects of implementing this change

ODKTokens with expires fields set to None will be inactivated

Before submitting this PR for review, please make sure you have:

  • Included tests
  • Updated documentation

Closes #2584

@FrankApiyo FrankApiyo changed the title When an odk token expires is nil, deactivate and replace When an odk token expires is None, deactivate and replace Apr 11, 2024
@FrankApiyo FrankApiyo force-pushed the deactivate-odk-tokens-with-no-expires branch from b0ae639 to efdfe80 Compare April 12, 2024 04:35
@FrankApiyo FrankApiyo merged commit 1afc2ce into main Apr 12, 2024
9 checks passed
@FrankApiyo FrankApiyo deleted the deactivate-odk-tokens-with-no-expires branch April 12, 2024 05:02
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.

NoneType Error when fetching ODK token
2 participants