Validate route name

[Axik]

Previously route name could take incorrect value with spaces, or numbers at start.
@asvetlov

[alexdutton]

Was this an issue? As far as I can tell, they're only ever used with getitem` and not attribute access, so they shouldn't cause any trouble if they contain silly characters.

I'd used colons for namespacing in my route names (e.g. 'oauth2:authorize'), which I would have thought would be reasonable.

[asvetlov]

Well, initial issue was using just literal text phrases for route names,
which is definitely wrong.
I agree to relax the rule for allowing identifiers separated by dots or
columns.

On Tue, Oct 20, 2015 at 11:41 AM Alexander Dutton [email protected]
wrote:

Was this an issue? As far as I can tell, they're only ever used with
getitem` and not attribute access, so they shouldn't cause any trouble
if they contain silly characters.

I'd used colons for namespacing in my route names (e.g.
'oauth2:authorize'), which I would have thought would be reasonable.

—
Reply to this email directly or view it on GitHub
#567 (comment).

Thanks,
Andrew Svetlov

[asvetlov]

Fixed by 0.18.1 release

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.