-
Request body parameters should all be in camel case to be consistent with the rest of the project
`firstName`
`lastName`
So on and so forth.
This should be updated on the frontend, backend,…
-
First, thank you for this project, it was exactly what we needed to backend `vault-secrets-operator` and fix the impact of the 16.x 1 year max token expiry that caught us out a few weeks back.
Now …
-
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…
-
Some traits have competing naming conventions for types within Bevy:
| Trait | Suffixes used | Suggestion |
|-|-|-|
| `SystemSet` | `System`, `Set`, `Systems`, no-suffix | Not obvious which to ch…
-
After discussion with ESA, the agreement was that the ancillary files with ephemeris and pointing info shoul be named:
solo_ANC_stix-aux-ephemeris_..._V...fits
To do: update pieces of code here a…
-
@Schiano-NOAA requests a review of the [ASAR function names](https://github.com/Schiano-NOAA/ASAR/tree/main/R) to ensure they make sense. I have a few non-blocking suggestions and questions below.
…
-
I would love more of the Circle Biomes such as 'Circle forest icon' and 'Mountains icon' and also for you to add a tag for the ones with a ring around them. The specific biomes I want is a desert, a v…
-
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…
-
Custom resources not used by SST need to be named, and we would like them to be normalized to SST convention.
Please expose the naming convention logic so that the library users can invoke for non-…
-
All attribut names referencing value lists should be prefixed by "fk_" such as horizontal_positioning ->fk_horizontal_positioning