-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add more complicated variable names #3
Comments
Yes. |
I've started on a few tests over here: https://github.com/damnhandy/uritemplate-test/blob/master/extended-tests.json Is this kind of what you were thinking @hannesg ? |
@damnhandy Yep, "last.name" and "Some%20Thing" are good examples. |
On second thought, I'm not so sure
My ABNF skills are far from awesome, but if I read that correctly, the |
According to that, not legal. Cheers, On 21/05/2012, at 11:28 AM, Ryan J. McDonough wrote:
Mark Nottingham http://www.mnot.net/ |
Nope, is legal. You can read the spec as following: A varspec is a varname optionally followed by a modifier-level4. It's legal but it may not be the first or last character. |
I think you're right @hannesg , I overlooked the quotes on |
argh, missed that, sorry; I should have looked more closely. |
You're welcome ;) |
Making the fix... |
Think we can close this for now (though there may be more...) |
Currently all variables are alpha-only. We could use some numbers, underscores, dots and pct-encoded characters ( see: http://tools.ietf.org/html/rfc6570#section-2.3 ).
The text was updated successfully, but these errors were encountered: