-
## Proposal
When adding a test to `libocpp` that partially (or fully) validates `libocpp`'s conformance to a functional requirement in an OCPP standard, prefix the name of the test with said function…
drmrd updated
3 weeks ago
-
## What
We should have a common way of translating base/modifier classes that exist in vanilla to props in `react-components`.
For example, the `help` prop in `Input` could be named `formHelpText`…
-
### Term Name
ods:hasRelatedPID
### Digital Object Name
DigitalSpecimen: TombstoneMetadata
### Feedback
This element contains an array of PIDs, however according to the [naming convention](https:…
-
Currently, URLs in our code that exceed 80 characters are split into two comments. However, this ends up making it tougher to copy paste and visit the URL, or open it directly using an editor.
Ind…
-
An update should be made to convention naming, because right now there are a few devices like:
Galaxy Tab A7 Lite 8.7" (2021) WiFi
Galaxy Tab A 10.1" WiFi (2016)
-
### Is your feature request related to a problem? Please describe.
Currently `CamelCaseStrategy` in `EnumNamingStrategies` assumes that enum entires in source code are named using UPPER_SNAKE_CASE …
-
We want to have an ability (extension point) to control default MDC keys. Now they are statically defined in workers.
Why it's important:
* we have multiple stacks: Java + Python and trying to uni…
-
Hello. First of all, thanks for the awesome work on this!
I wanted to bring up a minor issue regarding the naming convention used for the library classes. The official [Kotlin coding conventions gu…
-
Right now, we are using a mix of the PRs starting with a string like `[Editorial]` and `[html-aam]`, and, we have tags for these things. Maybe we should just do one or the other?
-
The naming conventions in this project are a bit inconsistent, so I'd like to clarify what's intended.
1. The Zig convention for namespaces is `snake_case`, however this project seems to use mostly…