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
We are using scope: 'path" because we like the way the URL's are formatted. Very "Resty"!
When the fields are set to scope: 'query' our GET works fine with Swagger UI.
When the optional fields (isRequired: false) are set to scope: 'path' a Javascript error occurs in the Swagger UI. Please see the following screen shot.
"filter is a required path param"
Here is a screen shot of the Swagger UI showing the fields.
We have played around with adding the "/:filter" to the url and changing various options in the validators.
I took a peak at the module source code. There is a lot of good code in there. My wild guess is that _pushPathParameters may need a fix. It doesn't take into consideration the isRequired option. Just a guess.
The text was updated successfully, but these errors were encountered:
We are using scope: 'path" because we like the way the URL's are formatted. Very "Resty"!
When the fields are set to scope: 'query' our GET works fine with Swagger UI.
When the optional fields (isRequired: false) are set to scope: 'path' a Javascript error occurs in the Swagger UI. Please see the following screen shot.
Here is a screen shot of the Swagger UI showing the fields.
Here is the definition of my route.
We have played around with adding the "/:filter" to the url and changing various options in the validators.
I took a peak at the module source code. There is a lot of good code in there. My wild guess is that _pushPathParameters may need a fix. It doesn't take into consideration the isRequired option. Just a guess.
The text was updated successfully, but these errors were encountered: