-
I have found it difficult to read the code in this repository and safe_dns at times due to lack of attention being paid for the amount of columns used (the Rust guidelines mandate 99 columns) and impo…
et4te updated
8 years ago
-
### Problem
We need to do a coding standards review.
For instance, we need to update this section :
https://github.com/inasafe/inasafe/wiki/Coding-Standards#strings-and-internationalisation
…
-
Standards for code style and format should be established and placed in a visible location like a contributor guide.
-
From [Coding Standards](https://hermes-core.readthedocs.io/en/latest/dev-guide/code_standards.html), `from packagename import *` should never be used (except in `__init__.py`).
hermes_instrument/te…
-
- [x] Find reputable style guides for C# and Unity and link to them here or the Wiki
- [ ] Discuss style guides. Agree on project/team standards
- [x] Document Standards in the Wiki for future …
-
We have just added a CICD pipeline that runs all tests upon pushing and merging code. However, we don't yet enforce a minimum code coverage. We should decide what standards we need and then enforce th…
-
We should have standards and conventions for code. (As mentioned during private chat between collaborators)
-
Ensure CMake style is consistent across projects. Note that linting is handled in a separate issue: #1132
This may involve building out a common set of CMake utilities.
But more likely just me…
-
Imposing and describing coding standards could lead to a readable and consistent code base and could make the process of contributing a patch easier for external developers. Existing PHP coding standa…
-
Name conventions, use of name spaces, etc.
I don't have a lot of opinions about this, happy to choose my favorites, or accommodate to others' choices, but we should specify the points, so we can conf…