-
Notifications
You must be signed in to change notification settings - Fork 54
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
Unrecognized param #620
Comments
I believe this is related to apiaryio/api-blueprint#69 |
@Neamar I think This is currently a bit in limbo. I agree that for users, However, for now, there is a problem with precent-encoded values as well. I do think those should be fixed as well -- in spec as well in snowcrash. |
Ok. So for now, there is no workarounds ? :( On Mon, Mar 24, 2014 at 3:24 PM, Almad notifications@github.com wrote:
|
This is a good question Currently a parameter identifier is expected to conform to:
But as of RFC 6570 variables it should be:
This is a bug and should be fixed in Snow Crash. An explicit note on URI template variables might be added to API Blueprint spec (most likely 1B). |
To be addressed with apiaryio/snowcrash#61 |
@Neamar opened apiaryio/snowcrash#90
(not sure i'm posting on right repo, since i'm using API blueprint from @danielgtaylor Aglio)
My API allow for parameters prefixed with "@", for instance "@name=".
However, describing such an endpoint result in the following error:
Where line 134 is:
However, i believe such a parameter is actually valid HTTP. Would it be possible to improve snowcrash to handle this use case ? (and possibly more exotic charsets).
I tried to HTML escape / encodeURIComponent without success.
The text was updated successfully, but these errors were encountered: