-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yada.swagger-parameters & yada.parameters are almost the same code. #315
Comments
so, when i swap out yada.swagger-parameters with yada.parameters my backend just breaks. even with minimal schema (map of 1 key and 1 value, no custom types). I think that it may be worth while to focus on 1 of these files, and get rid of the other. both files look like they have a bit of room for removing complexity, and adding flexibility/optimization. like, with the swagger file, i can add multimethods for ring-swagger, and get coercers working without modifying the files, but my coercers are at the lowest priority. also there isn't a single default coercer map, there are 3 or 4 or 5 of them in different files. |
i'm confused as to why the swagger one exists, and why it's the default param coercer in yada.
The text was updated successfully, but these errors were encountered: