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
{{ message }}
This repository was archived by the owner on Mar 18, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 18, 2019. It is now read-only.
Current Field specification is quite restrictive in terms of supported attributes. For example, if a final user is interested in rendering the specification using Swagger, there are several attributes like enum that can't be used right now. In order to make possible to add more attributes and not being coupled to a concrete rendering specification, would it be possible to add a dictionary attribute as part of the Field namedtuple for collecting them?. Then final renderers can use such dictionary for including more elements
We're building out better support for OpenAPI with 3.0, which will address some of this.
We might choose to flexibly support arbitrary extensions/attributes in the future, but not something I'd like to have just yet. However we probably will stop using immutable object types for 3.0.
Activity
lovelydinosaur commentedon Feb 15, 2018
We're building out better support for OpenAPI with 3.0, which will address some of this.
We might choose to flexibly support arbitrary extensions/attributes in the future, but not something I'd like to have just yet. However we probably will stop using immutable object types for 3.0.