Closed natanael closed 3 years ago
Hi,
I noticed that I could not get a info->description for a Field<T> in the oas file. This should fix that.
info->description
Field<T>
oas
I also took the chance to move all the AbstractPairList logic to a new method called generateSchemaForAbstractPairList.
AbstractPairList
generateSchemaForAbstractPairList
It would be super nice to be able to compare OAS before and after and good for testing, but that seemed too complicated to do right now.
Example:
DTO_FIELD_INFO(todoList) { info->description = "Task title -> task description"; }; DTO_FIELD(Fields<String>, todoList);
"todoList": { "type": "object", "description": "Task title -> task description", // <-- This was not showing "additionalProperties": { "type": "string" } },
Great work! Merged!
Also, I think it will be a good idea to come up with a general method to set common additional info (description + default) for all types.
Hi,
I noticed that I could not get a
info->description
for aField<T>
in theoas
file. This should fix that.I also took the chance to move all the
AbstractPairList
logic to a new method calledgenerateSchemaForAbstractPairList
.It would be super nice to be able to compare OAS before and after and good for testing, but that seemed too complicated to do right now.
Example: