Allow IDs to begin with a number
See original GitHub issueCurrent State: IDs are allowed to begin with a (‘a’…‘z’|‘A’…‘Z’|‘_’).
After implementing this feature:
IDs are allowed to begin with (‘a’…‘z’|‘A’…‘Z’|‘_’|‘0’…‘9’). However, to allow separation from e.g. integer, IDs cannot exist solely of numbers.
Examples
3-Axis as int // Correct
3-Axis2 as int // Correct
5635 as int // Incorrect
axis as int // Correct
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
What are valid values for the id attribute in HTML?
For HTML 4, the answer is technically: ID and NAME tokens must begin with a letter ([A-Za-z]) and may be followed by any...
Read more >The id attribute got more class y in HTML5 - Mathias Bynens
The HTML 4.01 spec states that ID tokens must begin with a letter ( [A-Za-z] ) and may be followed by any number...
Read more >How EINs are Assigned and Valid EIN Prefixes - IRS
Learn how EINs are assigned and view a list of valid EIN prefixes by campus/location.
Read more >Unique ID Numbers | Identification for Development - ID4D
In the context of foundational systems, ID numbers are considered to be “unique” when: the number-generating process ensures that no two people within...
Read more >Use number matching in multifactor authentication (MFA ...
Enable number matching in the portal To enable number matching in the Azure AD portal, complete the following steps: In the Azure AD...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I agree that most of the compilers don’t allow this. However the Vorto device descriptions should be technology agnostic - and we need a way for specifying these “original” names. Currently LWM2M related models are affected by this constraint. Wouldn’t it make sense to adapt the code generator infrastructure accordingly?
Original names can be put in mappings, e.g. LWM2M Mappings. Processing of these kind of variable names is going to be more complex. Most languages do not support it for good reasons 😃