daenamnu/discordeno
1
0
Fork 0
mirror of https://github.com/discordeno/discordeno.git synced 2026-09-17 08:47:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

style: move to deno fmt (#1992)

Browse Source 
* Create deno.json

* run format

* run format

* ci: only check formatting

* f

* Update settings.json

* Update settings.json
This commit is contained in:
ITOH
2022-02-04 15:00:04 +01:00
committed by GitHub
parent 637e2c2a90
commit 81f8e0377c
259 changed files with 1731 additions and 1795 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/CONTRIBUTING.md
+12 -16
View File
@@ -2,12 +2,10 @@
- Read the [style guide](#style-guide).
- Ask for help on the [official Discord server](https://discord.gg/ddeno)
- If you are going to work on an issue, mention so in the issue comments before
you start working on the issue.
- If you are going to work on a new feature, create an issue and discuss with
other contributors before you start working on the feature.
- Abide by and heed to
[Discord Developer Terms of Service](https://discord.com/developers/docs/legal)
- If you are going to work on an issue, mention so in the issue comments before you start working on the issue.
- If you are going to work on a new feature, create an issue and discuss with other contributors before you start
working on the feature.
- Abide by and heed to [Discord Developer Terms of Service](https://discord.com/developers/docs/legal)
## Submitting a Pull Request
@@ -22,15 +20,14 @@
- File names shall use camel case.
- Comply with
[these guidelines for inclusive code](https://chromium.googlesource.com/chromium/src/+/master/styleguide/inclusive_code.md).
- An exported function must not have more than 4 individual parameters, the rest
arguments should be incorporated inside an object as a single parameter.
- Export all interfaces, types, and enums that are used for or inside an
exported entity.
- Every exported entity must be accompanied by a Typedoc (JSDoc without explicit
types) comment block. Ideally, we prefer single line comment block.
- An exported function must not have more than 4 individual parameters, the rest arguments should be incorporated inside
an object as a single parameter.
- Export all interfaces, types, and enums that are used for or inside an exported entity.
- Every exported entity must be accompanied by a Typedoc (JSDoc without explicit types) comment block. Ideally, we
prefer single line comment block.
- Top-level functions should not use arrow syntax.
- Minimize dependencies (do not add a dependency unless it is absolutely
necessary and has been discussed on the Discord Server).
- Minimize dependencies (do not add a dependency unless it is absolutely necessary and has been discussed on the Discord
Server).
- Do not make circular imports.
- Utilize functional API wherever possible and avoid usage of ES6 classes.
- Please follow the
@@ -45,8 +42,7 @@
## Types Guide
- Must use camel case (same property name as in the docs just in camel case).
- Each field or property must be accompanied with a reasonable JSDoc comment
right above its type definition.
- Each field or property must be accompanied with a reasonable JSDoc comment right above its type definition.
- Must be placed inside of the types module (in `src/types` directory).
Example: