Inconsistent nomenclature of aliases
See original GitHub issueDescribe the problem
Some packages have a hyphenated alias, other use camelcase. Is there a reason for this?
alias: "databaseManager",
alias: "error-tracker",
alias: "error-tracker",
alias: "event-emitter",
alias: "json-rpc",
alias: "logManager",
alias: "transactionPool",
alias: "vote-report"
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Consistency, Inconsistency, and Ambiguity of Metabolite ...
Every database uses its own namespace which is a particular set of identifiers (such as numerical tags or names) for metabolites and reactions: ......
Read more >Effects and remedy for inconsistency in name pattern
1. Stick to the names on your birth certificate · 2. National recognition of name order begins with O level certificate · 3....
Read more >Inconsistent use of column name aliases when replacing a ...
Inconsistent use of column name aliases when replacing a data source. I have a workbook which I want to be able to hook...
Read more >Don't Confuse Readers With Inconsistent Character Names
Your characters can have all the nicknames and code names in the world, but do your readers a favor and consistently refer to...
Read more >Last Name First - No Joking Matter! | U.S Immigration Law
In this article, we examine the importance of being consistent with one's name among various documents, the hierarchy of certain documents that ...
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
Sure, also open a PR for the 2.3 migration guide on docs.ark.io as plugins might be affected by this.
This issue has been closed. If you wish to re-open it please provide additional information.