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.
feat(auth): add JWT token revocation with Redis blocklist #439
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
base: main
Are you sure you want to change the base?
feat(auth): add JWT token revocation with Redis blocklist #439
Changes from all commits
9a3d0e816838b6ccd424e0e976198561a3e52a3660File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check failure on line 143 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 201 — creates event and returns it for authenticated organizer
Check failure on line 168 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 400 — rejects missing required fields (no dates, no location)
Check failure on line 174 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 400 — rejects missing location
Check failure on line 179 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 400 — rejects location shorter than 2 characters
Check failure on line 184 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 400 — rejects location longer than 100 characters
Check failure on line 189 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 400 — rejects event name shorter than 3 characters
Check failure on line 195 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 400 — rejects event name longer than 100 characters
Check failure on line 203 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 400 — rejects invalid date format
Check failure on line 219 in apps/backend/src/__tests__/event.test.ts
src/__tests__/event.test.ts > Events API > POST /api/events — create event > 201 — generates a unique slug when the first candidate is taken
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.