Skip to content
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

Add body for default ResourceNotFound error #285

Open
demeyerthom opened this issue Oct 16, 2023 · 0 comments
Open

Add body for default ResourceNotFound error #285

demeyerthom opened this issue Oct 16, 2023 · 0 comments

Comments

@demeyerthom
Copy link

Currently in api-specs/api/traits/errorable.raml the 404 response is missing a body description. During code generation this causes the Go code generator to skip generating a typed error for a ResourceNotFound response, defaulting to a GenericRequestError instead. I believe this happens because the 404 error gets filtered from the possible responses before being passed to the code generation method.

Would it be possible to add this body to the RAML definitions? Or do you maybe have other suggestions on how to deal with this type of missing body in described responses? I have tried hardcoding a 404 response in the code generation, but this conflicts with potential other raml definitions where there is a fully described 404.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant