-
Notifications
You must be signed in to change notification settings - Fork 2
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
Naming convention: Clarification wanted #356
Comments
|
Definition accepted, access not.
The second line causes:
This needs to be fixed. |
I still stumble about the naming convention like written down in #206 (comment) There is a lot of redundancy and not all aspects are clarified. After thinking about, this is my version now:
Any other character than letters, digits and Open questions: (1) How to handle leading and trailing blanks or tabs (allowed in pure JSON, but not preferred)?
Shall this cause an error or shall the JsonPreprocessor automatically make a conversion to:
in such a case? (2) How to handle the backslash? Is allowed in pure JSON, but must be masked. Therefore this should be allowed in general:
But JsonPreprocessor throws an error. Is there a certain reason for the JsonPreprocessor to deviate from JSON standard here? |
Reworked version:
|
I would like to understand the naming convention in more detail.
#206 (comment)
(1)
W.r.t. "Alphanumeric Characters: Use letters (a-z, A-Z) and digits (0-9)."
Also 2, 3 and 4 byte characters are possible in between. Therefore the statement "Use letters (a-z, A-Z)" is outdated. Please update.
(2)
W.r.t. "Key names can contain the operator characters: +, -, and *"
A lot of non alphanumeric characters are not allowed. OK so far. But is there a certain reason, to allow especially +, -, and *? What is the use case? It would be worth to mention this in documentation.
(3)
How about '
/
'? This character is not mentioned in naming convention."par/am1" : "value"
is accepted. OK nor not?(4)
How about blanks inside key names (
"par am" : "value"
)? Currently this is accepted. OK nor not?The text was updated successfully, but these errors were encountered: