-
Related to https://github.com/RConsortium/S7/issues/453
I am working on implementing S7 classes for [arcgisutils](https://github.com/R-ArcGIS/arcgisutils/) and one thing I'm not quite sure on is ho…
-
Could you remove or make it optional for naming conventions when scaffold, it makes really annoying when it adds or removes an 's' in the names of things , so i have to change everything manually, thi…
-
The new state containers/storage introduce in #7 are looking pretty elegant. Was surprised how nicely it worked with the RBPF and how it was completely generic to the inner distribution type.
If we…
-
Currently I don't use code generation, because I'm not able to provide a custom name for the providers in my app. The naming convention in my app for providers is like this: "providerCurrentAppUser", …
-
We have EHDSObservation, then observationDate, observationCode.
Other models don't replicate the name.
We should define AND apply the convention for consistent element names
-
### Standardize Neighborhood Naming Conventions
Currently, the neighborhood data used across all datasets is inconsistent. To unify the naming conventions, let's follow these steps:
#### Tasks:
…
-
Description
For Conversations and collections, spaces are removed from FE side but preserved on Be side
For Prompts agents and datastores , spaces are not removed on FE side
**Steps to reproduce:**…
-
We need to establish a standard naming convention for data components in Harvest. The current model establishes two names: `ephemeral` and `persistent`, but this is ultimately inflexible. Instead, we …
-
### Summary
Colour variables and naming conventions
### Description
Our current colour variable setup is a bit limited, and we use of var colours sometimes in wrong places. A border colour on a back…
-
Morning, this looks really interesting, In the section below
>In most cases, the name of the entity is included at the beginning of the property key, but not any parent entities.
>
>For instan…