Ambiguous component name error does not mention first character cannot be numeric.
See original GitHub issueWhen assigning a component name, it is matched against a regex that does not allow the first character of the name to be numeric. However, the error thrown only mentions that the component name has to be alphanumeric:
Invalid component name: "0650475a". Component names can only contain alphanumeric characaters and the hyphen.
Other than the typo ‘characaters’, the provided component name also matches the condition of the error. It would be helpful if ~either the regex or~ the error is changed accordingly.
Thank you in advance!
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
ERROR: "The first character in this name cannot be a number
This issue occurs when the name of the file is provided as a number in the beginning of the file name. Example. 1.txt;...
Read more >9 Error messages | The tidyverse style guide
An error message should start with a general statement of the problem ... be a numeric vector, not a character vector. dplyr::nth(1:10, 1:2)...
Read more >alloy - This name is ambiguous due to multiple matches
A type error has occured: This name is ambiguous due to multiple matches: field this/Port <: belongsTo field this/Component <: belongsTo.
Read more >Error Explanations for The W3C Markup Validation Service
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies...
Read more >Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
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 FreeTop 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
Top GitHub Comments
I understand that, but maybe the error message can highlight this fact?
Interestingly your issue just revealed a typo in Vue’s source code. I’ll see to that too.