feat(server): Allow worker scopes for tokens #3533
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't require email addresses for special tokens
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3533 +/- ##
==========================================
- Coverage 48.44% 48.42% -0.02%
==========================================
Files 596 596
Lines 42232 42245 +13
Branches 1391 1391
==========================================
Hits 20459 20459
- Misses 21604 21617 +13
Partials 169 169 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
thinknoack
approved these changes
Aug 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a dataset:worker scope to the API. Allows the worker to make automated requests to the API with the scope of updating a single dataset.
This also corrects an issue where special tokens that never contain emails would occasionally throw an error where the request should have succeeded by checking the email state after the special cases.