You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For clients using the openAPI spec, it would be useful to know which fields are only expected to be in the output and not required to be set in the input.
We can use the OUTPUT_ONLYfield_behaviour flag to annotate these types of fields.
For example, by setting the field behaviour to OUTPUT_ONLY on the project field, the typescipt generated field is readonly.
For clients using the openAPI spec, it would be useful to know which fields are only expected to be in the output and not required to be set in the input.
We can use the
OUTPUT_ONLY
field_behaviour flag to annotate these types of fields.For example, by setting the field behaviour to
OUTPUT_ONLY
on the project field, the typescipt generated field isreadonly
.becomes:
We currently determine if a field is output-only by putting a comment on top of the field. For example:
minder/proto/minder/v1/minder.proto
Lines 3175 to 3177 in cda126f
This task involves finding all the fields that are documented as output-only and setting the field_behaviour flag on them.
The text was updated successfully, but these errors were encountered: