fix: add auth schemes for open api spec#1059
Merged
Merged
Conversation
Coverage Report for CI Build 25004573566Coverage increased (+0.05%) to 71.601%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats💛 - Coveralls |
ecfbab4 to
912eacb
Compare
ferhatelmas
reviewed
Apr 27, 2026
| "test:integration:watch": "vitest --config vitest.integration.config.ts", | ||
| "test:integration:coverage": "vitest run --coverage --config vitest.integration.config.ts", | ||
| "test": "npm run infra:restart && npm run test:dummy-data && npm run test:integration", | ||
| "test": "npm run infra:restart && npm run test:dummy-data && npm run test:integration && npm run test:unit", |
Member
There was a problem hiding this comment.
maybe change order to get faster feedback
ferhatelmas
approved these changes
Apr 27, 2026
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
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.
What kind of change does this PR introduce?
fix to open api specs
What is the current behavior?
Open API spec does not include auth schemes. This makes the swagger UI unusable as you cannot authenticate
What is the new behavior?
Add auth schemes to all authenticated endpoints (api and admin api). This makes the open api json more accurate and also enables authentication in the swagger UI when developing which allows executing endpoints directly in the swagger UI (http://localhost:5000/documentation)