-
I think there should be a code style guide.
-
we have to significantly improve contribution experience
- build with docker
- migrate to deno
- build to ipfs
- get rid of node
- and only after contribution guide
-
OpenLayers' code should be more consistent in its style. Suggestions: http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml or good old Crockford: http://javascript.crockford.com/code.…
-
I want to suggest sticking to the code style for all our codebase. As example for JavaScript we can use Google JavaScript Style Guide https://google.github.io/styleguide/jsguide.html. Any thoughts on …
-
Now, I'm using default firebase functions code style for linting (with eslint), but I'm pretty open to anything we feel confortable with. Discussion open ^^
My 50 cents: I preffer indent using tabs…
-
### Python
[Python Official Style Guide](https://peps.python.org/pep-0008/)
[Google Python Style Guide](http://google.github.io/styleguide/pyguide.html)
Tools list:
- auto-formatter: [Black](ht…
-
* **Electron-Builder Version**: `22.10.5`
* **Node Version**: `14.6.0`
* **Electron Version**: `12.2.2`
* **Target**: **Windows** (for this issue)
> This issue is a description of a problem my …
-
### Problem
Currently, the frontend guide helps you get started and understand how to write `urql` queries. However, it does not outline conventions and best practices for implementing actual React…
-
Many of our [guides](https://github.com/opensearch-project/opensearch-js/tree/2.4/guides) were almost copied and pasted from the Ruby guides without adapting to the JS client. We need to go through al…
-
This is a loose collection of code style rules that contributions to this project should follow:
## SwiftLint
The rules laid down in `.swiftlint.yml` apply and code submitted to the project should…