Ensure valid route alias names

[xfra35]

I think that the regex in $f3->route() is a bit too permissive for aliases. It allows nearly all characters, in particular dots, while it should stick to the \w range.

What drew my attention is an issue for my f3-access plugin where the user has defined aliases with dots: xfra35/f3-access#4

Additionally, there's that ? after @ which seems superfluous to me. But I could be missing something.

[ikkez]

We had \w+ before, and the change to .+? was introduced not that far ago and it seems to be made on purpose, see this blame: a27f2f0
Perhaps it was also regarding some unicode support 🤔

[xfra35]

You're right, thanks.

@bcosca what was the reason of the tweak in route() regex in commit a27f2f0?

Was it to allow unicode characters in route aliases? If yes, we should forbid dots and make the regex consistent in mock() as well as in the second part of the route() regex.

[bcosca]

You're absolutely right. The intent of that commit was to allow for unicode characters.

[ikkez]

fixed in 5164e8c