-
To make it easier to contribute and for ourselves to have a consistent codebase, we should document some of our coding conventions.
- Always provide ref through `forwardRef` (unless exposing a Cont…
-
MigrationHistoryTable constructs a mini-model in order to generate the migration command for the creation of the history table in the database ([code](https://github.com/dotnet/efcore/blob/main/src/EF…
-
- How do we want to manage contributions to the repository?
- Merge, rebase or squash and merge PRs into main?
- What determines acceptability to merge?
- Disallow pushes directly to main
- Set up aut…
-
I suggest we take a look at the following:
https://github.com/emberjs/ember.js/blob/master/STYLEGUIDE.md
https://github.com/softlayer/ember-style-guide
There are some differences, so I would use the…
-
# User Story
## Story
As a Maintainer
I want to know the coding conventions that apply to this project
so that I can contribute appropriately to the product.
## Acceptance Criteri…
-
### Overview
There are field names in the code that do not currently match our documentation. We need to go through the existing django models, identify the mismatches, and update the code or docum…
-
Document code using docstrings following [Google docstring conventions](https://google.github.io/styleguide/pyguide.html#38-comments-and-docstrings).
We could also check the [other Google conventio…
-
This came up at the Dev call today, but we should consider putting together a standard Contribution Guide and include it in the repo and RTD. It should include:
- Code formatting standards (`black`)…
-
Semi-related to #1426, it would be great if UniFFI could generate Swift function/variable/argument/type names that conform to the “Follow case conventions” point in the [Swift API Design Guidelines](h…
-
The coding conventions of IfcOpenShell seem rather mixed. What would be the "official" conventions to follow when I start to contribute?