You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,19 +13,19 @@ in your text editor or IDE of your choice to ensure builds from GitHub Actions d
13
13
5. Commit your changes, and push them.
14
14
6. Submit a Pull Request [here]!
15
15
16
-
## Char Concept Guidelines
16
+
## Canvas Constructor Concept Guidelines
17
17
18
18
There are a number of guidelines considered when reviewing Pull Requests to be merged. _This is by no means an exhaustive list, but here are some things to consider before/while submitting your ideas._
19
19
20
-
- Everything in Char should be generally useful for the majority of users. Don't let that stop you if you've got a good concept though, as your idea still might be a great addition.
21
-
- Everything should follow [OOP paradigms] and generally rely on behaviour over state where possible. This generally helps methods be predictable, keeps the codebase simple and understandable, reduces code duplication through abstraction, and leads to efficiency and therefore scalability.
22
-
- Everything should follow our ESLint rules as closely as possible, and should pass lint tests even if you must disable a rule for a single line.
23
-
- Scripts that are to be ran outside of the scope of the bot should be added to [scripts] directory and should be in the `.mjs` file format.
20
+
-Everything in Canvas Constructor should be generally useful for the majority of users. Don't let that stop you if you've got a good concept though, as your idea still might be a great addition.
21
+
-Everything should follow [OOP paradigms] and generally rely on behaviour over state where possible. This generally helps methods be predictable, keeps the codebase simple and understandable, reduces code duplication through abstraction, and leads to efficiency and therefore scalability.
22
+
-Everything should follow our ESLint rules as closely as possible, and should pass lint tests even if you must disable a rule for a single line.
23
+
-Scripts that are to be ran outside of the scope of the bot should be added to [scripts] directory and should be in the `.mjs` file format.
0 commit comments