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
The following “globally allowed characters” MAY be used anywhere in a member name:
...
U+0080 and above (non-ASCII Unicode characters; not recommended, not URL safe)
So whilst they're not recommended, we could have a config setting that enables engineers to opt-in to say "Yes, these characters aren't URL safe, but I have no choice" and therefore loosen our validation regexp's.
I wonder how things like Swagger and GraphQL deal with unicode characters...
According to the spec, unicode can be appeared in names, but below check prevent that
https://github.com/holidayextras/jsonapi-server/blob/master/lib/jsonApi.js#L57
The unicode world need this feature, could add unicode support?
The text was updated successfully, but these errors were encountered: