Marking properties in Open API as required #87
Replies: 1 comment
-
Ticket #98 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@TylerMatteo Should we be more diligent in marking properties/parameters as required in the Open API documentation? I noticed that when we neglect to mark them, Kubb marks them as possible undefined. I think this will lead to more defensive programming than necessary- checking for
undefined
values where they will never reasonably occur (because an error would have occurred first).Relevant to any @NYCPlanning/open-source-engineering writing documentation
Beta Was this translation helpful? Give feedback.
All reactions