chore: define openapi specification for dem-gateway (MAPCO-9813) #14
Conversation
vitaligi
commented
Feb 8, 2026
vitaligi
commented
| Question | Answer |
|---|---|
| Bug fix | ✖ |
| New feature | ✖ |
| Breaking change | ✖ |
| Deprecations | ✖ |
| Documentation | ✖ |
| Tests added | ✖ |
| Chore | ✔ |
|
🎫 Related Jira Issue: MAPCO-9813 |
| schemas: | ||
| error: | ||
| Classification: | ||
| type: string |
There was a problem hiding this comment.
Why is it a string and not a number? with range limit?
There was a problem hiding this comment.
currently Classification will continue to be string for cross team consistency
openapi3.yaml
Outdated
| - classification | ||
| properties: | ||
| classification: | ||
| $ref: '#/components/schemas/Classification' |
There was a problem hiding this comment.
Why do we need a specific method on changing classification?
There was a problem hiding this comment.
We need specific instructions on publish/ unpublish
| inputFiles: | ||
| allOf: | ||
| - $ref: '#/components/schemas/InputFiles' | ||
| ValidateSuccessfulResponse: |
There was a problem hiding this comment.
For a valid response, I've expected something like:
components:
schemas:
validateResponse:
type: object
required:
- isValid
- message
- code
properties:
isValid:
type: boolean
message:
type: string
code:
type: string
enum:
- SUCCESS
- MISSING_CREDENTIALS
- INVALID_CREDENTIALS
- INVALID_RECORD_NAME
- INTERNAL_ERROR
2 participants
