feat: API specs update for version latest#52
feat: API specs update for version latest#52appwrite-specs[bot] wants to merge 1 commit intomainfrom
Conversation
Greptile SummaryAdds discriminator support to the Confidence Score: 5/5Safe to merge; changes are well-formed and both specs are internally consistent. Only finding is a P2 suggestion to add an enum constraint to the discriminator property in both schemas — no blocking issues. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "chore: update API specs and SDK examples" | Re-trigger Greptile |
| "type": { | ||
| "type": "string", | ||
| "description": "Provider repository list type.", | ||
| "x-example": "framework" | ||
| } |
There was a problem hiding this comment.
Missing
enum constraint on discriminator property
The type field is used as the discriminator property but is declared as an unconstrained string. Each schema should restrict the discriminator to exactly the value it represents so validators and code generators can enforce the mapping. The same applies to providerRepositoryRuntimeList.type.
| "type": { | |
| "type": "string", | |
| "description": "Provider repository list type.", | |
| "x-example": "framework" | |
| } | |
| "type": { | |
| "type": "string", | |
| "description": "Provider repository list type.", | |
| "enum": ["framework"], | |
| "x-example": "framework" | |
| } |
This PR contains API specification updates for version latest.