-
We don't want camelsInFilenames.
Will probably add a rule to make check-censored later.
-
Currently (from a quick glimpse over the readme), it seems like this module uses `snake_case` for various properties, even though the usual JS recommendation (and most style-guides as well) would reco…
-
### Suggestion
The parameter name `banned_IPs` in the JSON object returned by the method `preferences` must be renamed because the automatic conversion methods from `camel to snake` of most programma…
-
The last draft of OParl uses CamelCase (reason: compatibility with RDF conventions). Popolo prefers snaked_case (reason: compatibility with ORMs):
> If an implementation serializes to JSON, its seria…
-
I am using LanguageTool to verify API documentation. Some documentation fragments include variable names in snake_case.
It would be very helpful to have a speller option to ignore words in snake ca…
-
I'm going through the directories now and feel there is a lot of convention clean up needed:
- [x] CamelCase for file names should be reserved for Modules. For non-modules, just use snake_case
- […
-
-
### What is the problem this feature would solve?
When using Eden for frontend development, we currently have to access snake case API endpoints in a bracket notation, like api['sign-in'].post. This …
DoK6n updated
2 months ago
-
While investigating snapshot creation for earlier versions (PR #322), I uncovered an inconsistency in how checkpoint metadata fields are named in the `_last_checkpoint` file.
**Current Behavior:**
…
-
I read your paper in a bout of insomnia this past night, and found that it was really fascinating and thoughtful. I came to your work by the way of this other paper https://arxiv.org/pdf/2401.03910.pd…