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
Currently, we have a setup where we generate json-schema/swagger documentation from spec the following way:
Every spec we declare that contains a {:name ...} attribute becomes a top-level schema;
When a top-level schema is used to compose another top-level schema such as (s/keys :req-un [::something]), it is declared as a $ref instead of inlining the definition.
This works fine for most specs. However, those that we declare as s/keys or s/map-of end up including a stringified name of itself when it doesn't have an explicit :name assigned.
To circumvent that, I've created this local version:
Hi, first of all thanks for spec-tools.
Currently, we have a setup where we generate json-schema/swagger documentation from spec the following way:
{:name ...}
attribute becomes a top-level schema;(s/keys :req-un [::something])
, it is declared as a$ref
instead of inlining the definition.This works fine for most specs. However, those that we declare as
s/keys
ors/map-of
end up including a stringified name of itself when it doesn't have an explicit:name
assigned.To circumvent that, I've created this local version:
However, I think it'd be best if it was something like this:
or
Does this make sense?
Thanks in advance,
Henry Kupty
The text was updated successfully, but these errors were encountered: