forked from Aircoookie/WLED
-
Notifications
You must be signed in to change notification settings - Fork 131
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #192 from atuline/dev
- Loading branch information
Showing
137 changed files
with
17,561 additions
and
8,434 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
name: Bug Report | ||
description: File a bug report | ||
labels: ["bug"] | ||
body: | ||
- type: markdown | ||
attributes: | ||
value: | | ||
Please quickly search existing issues first before submitting a bug. | ||
- type: textarea | ||
id: what-happened | ||
attributes: | ||
label: What happened? | ||
description: A clear and concise description of what the bug is. | ||
placeholder: Tell us what the problem is. | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: how-to-reproduce | ||
attributes: | ||
label: To Reproduce Bug | ||
description: Steps to reproduce the behavior, if consistently possible. | ||
placeholder: Tell us how to make the bug appear. | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: expected-behavior | ||
attributes: | ||
label: Expected Behavior | ||
description: A clear and concise description of what you expected to happen. | ||
placeholder: Tell us what you expected to happen. | ||
validations: | ||
required: true | ||
- type: dropdown | ||
id: install_format | ||
attributes: | ||
label: Install Method | ||
description: How did you install WLED? | ||
options: | ||
- Binary from WLED.me | ||
- Self-Compiled | ||
validations: | ||
required: true | ||
- type: input | ||
id: version | ||
attributes: | ||
label: What version of WLED? | ||
description: You can find this in by going to Config -> Security & Updates -> Scroll to Bottom. Copy and paste the entire line after "Server message" | ||
placeholder: "e.g. WLED 0.13.1 (build 2203150)" | ||
validations: | ||
required: true | ||
- type: dropdown | ||
id: Board | ||
attributes: | ||
label: Which microcontroller/board are you seeing the problem on? | ||
multiple: true | ||
options: | ||
- ESP8266 | ||
- ESP32 | ||
- Other | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: logs | ||
attributes: | ||
label: Relevant log/trace output | ||
description: Please copy and paste any relevant log output if you have it. This will be automatically formatted into code, so no need for backticks. | ||
render: shell | ||
- type: textarea | ||
attributes: | ||
label: Anything else? | ||
description: | | ||
Links? References? Anything that will give us more context about the issue you are encountering! | ||
Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. | ||
validations: | ||
required: false | ||
- type: checkboxes | ||
id: terms | ||
attributes: | ||
label: Code of Conduct | ||
description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Aircoookie/WLED/blob/master/CODE_OF_CONDUCT.md) | ||
options: | ||
- label: I agree to follow this project's Code of Conduct | ||
required: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,10 @@ | ||
{ | ||
// See http://go.microsoft.com/fwlink/?LinkId=827846 | ||
// for the documentation about the extensions.json format | ||
"recommendations": [ | ||
"platformio.platformio-ide" | ||
] | ||
} | ||
{ | ||
// See http://go.microsoft.com/fwlink/?LinkId=827846 | ||
// for the documentation about the extensions.json format | ||
"recommendations": [ | ||
"platformio.platformio-ide" | ||
], | ||
"unwantedRecommendations": [ | ||
"ms-vscode.cpptools-extension-pack" | ||
] | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
## Thank you for making WLED better! | ||
|
||
Here are a few suggestions to make it easier for you to contribute! | ||
|
||
### Code style | ||
|
||
When in doubt, it is easiest to replicate the code style you find in the files you want to edit :) | ||
Below are the guidelines we use in the WLED repository. | ||
|
||
#### Indentation | ||
|
||
We use tabs for Indentation in Web files (.html/.css/.js) and spaces (2 per indentation level) for all other files. | ||
You are all set if you have enabled `Editor: Detect Indentation` in VS Code. | ||
|
||
#### Blocks | ||
|
||
Whether the opening bracket of e.g. an `if` block is in the same line as the condition or in a separate line is up to your discretion. If there is only one statement, leaving out block braches is acceptable. | ||
|
||
Good: | ||
```cpp | ||
if (a == b) { | ||
doStuff(a); | ||
} | ||
``` | ||
|
||
```cpp | ||
if (a == b) | ||
{ | ||
doStuff(a); | ||
} | ||
``` | ||
|
||
```cpp | ||
if (a == b) doStuff(a); | ||
``` | ||
|
||
There should always be a space between a keyword and its condition and between the condition and brace. | ||
Within the condition, no space should be between the paranthesis and variables. | ||
Spaces between variables and operators are up to the authors discretion. | ||
There should be no space between function names and their argument parenthesis. | ||
|
||
Good: | ||
```cpp | ||
if (a == b) { | ||
doStuff(a); | ||
} | ||
``` | ||
|
||
Not good: | ||
```cpp | ||
if( a==b ){ | ||
doStuff ( a); | ||
} | ||
``` | ||
|
||
#### Comments | ||
|
||
Comments should have a space between the delimiting characters (e.g. `//`) and the comment text. | ||
Note: This is a recent change, the majority of the codebase still has comments without spaces. | ||
|
||
Good: | ||
``` | ||
// This is a comment. | ||
/* This is a CSS inline comment */ | ||
/* | ||
* This is a comment | ||
* wrapping over multiple lines, | ||
* used in WLED for file headers and function explanations | ||
*/ | ||
<!-- This is an HTML comment --> | ||
``` | ||
|
||
There is no set character limit for a comment within a line, | ||
though as a rule of thumb you should wrap your comment if it exceeds the width of your editor window. | ||
Inline comments are OK if they describe that line only and are not exceedingly wide. |
Oops, something went wrong.