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/ISSUE_TEMPLATE/feature_request.yml
+4-4
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
name: "New feature proposal \U0001FA90"
1
+
name: New feature proposal 🪐
2
2
description: Propose a new feature to be added to TresJS
3
-
labels: ["enhancement"]
3
+
labels: [enhancement]
4
4
body:
5
5
- type: markdown
6
6
attributes:
@@ -10,15 +10,15 @@ body:
10
10
id: feature-description
11
11
attributes:
12
12
label: Description
13
-
description: "Clear and concise description of the problem. Please make the reason and usecases as detailed as possible. If you intend to submit a PR for this issue, tell us in the description. Thanks!"
13
+
description: 'Clear and concise description of the problem. Please make the reason and usecases as detailed as possible. If you intend to submit a PR for this issue, tell us in the description. Thanks!'
14
14
placeholder: As a developer using TresJS I want [goal / wish] so that [benefit].
15
15
validations:
16
16
required: true
17
17
- type: textarea
18
18
id: suggested-solution
19
19
attributes:
20
20
label: Suggested solution
21
-
description: "In module [xy] we could provide following implementation..."
21
+
description: 'In module [xy] we could provide following implementation...'
Copy file name to clipboardexpand all lines: CODE_OF_CONDUCT.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -28,16 +28,16 @@ Project maintainers are responsible for clarifying the standards of acceptable b
28
28
29
29
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30
30
31
-
##Scope
31
+
##Scope
32
32
33
33
This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
34
35
-
##Enforcement
35
+
##Enforcement
36
36
37
37
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team by DM at [TresJS Discord](https://discord.gg/UCr96AQmWn). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
38
39
39
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.
40
40
41
-
##Attribution
41
+
##Attribution
42
42
43
43
This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,6 @@ Before opening a pull request, make sure to run `pnpm lint` to make sure the cod
72
72
- Create a `fix/{issue-number}-fix-test-in-core` branch for this bug fix.
73
73
- If you are resolving a special issue, add `(fix #xxx[,#xxx])` (#xxx is the issue id) in your PR title for a better release log, e.g. `update entities encoding/decoding (fix #3899)`.
74
74
75
-
##Keep core small
75
+
##Keep core small
76
76
77
77
The core package should be as small as possible, it should only contain the core functionality of the library. If you are adding a new feature, please consider adding it as a plugin instead, for example, if you want to add support for [Effect Composer](https://threejs.org/examples/?q=compo#webgl_postprocessing_effectcomposer) you should create a new package called `@tresjs/postprocessing` and add it as a plugin. If it's a smaller scope you can always add it to `cientos` package.
0 commit comments