Closed dnephin closed 9 years ago
I am not sure why swagger-spec
mentions it as a warning. In a correct 1.2 spec, declaring a model with the name File
would mean using a $ref
for the model. If File
is assigned as a type, the only intent will be to use it as a multipart
file param and not a model. Warning would make much more sense if checking the assignment of File
on ref
?
The reason it gives is "[it] may lead to various conflicts with third party tools and SHOULD be avoided."
Not really clear
I think I know how to resolve this TODO I added, going to try it out
Fixed, and added a couple unit tests
https://github.com/swagger-api/swagger-spec/blob/master/versions/1.2.md#43-data-types
I don't see an easy way to do the extra assertions about being in params and type form. The warning comes right from the spec: https://github.com/swagger-api/swagger-spec/blob/master/versions/1.2.md#435-file