Hello, OpenAPI specs supports having readonly fields in entity that are being sent in POST/PUT requests.
The purpose of that is that basically you can have the same entity going back and forth but only the server is allowed to update it - so you can mark it as required but readonly.
Zudoku is not showing them as "readonly" in the request section - that could be a fast way to at least represent that/workaround the problem.
Gitlab on the other hands is, for example, directly hiding them - which is somewhat even better in terms of presentation.
Hello, OpenAPI specs supports having readonly fields in entity that are being sent in POST/PUT requests.
The purpose of that is that basically you can have the same entity going back and forth but only the server is allowed to update it - so you can mark it as required but readonly.
Zudoku is not showing them as "readonly" in the request section - that could be a fast way to at least represent that/workaround the problem.
Gitlab on the other hands is, for example, directly hiding them - which is somewhat even better in terms of presentation.