Skip to content

Commit b9432bf

Browse files
weinStagweinStag
committed
fix: normalize line endings to LF for all files
1 parent 4ec6cda commit b9432bf

File tree

192 files changed

+40124
-39544
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

192 files changed

+40124
-39544
lines changed

‎.dockerignore

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,21 @@
1-
node_modules
2-
npm-debug.log
3-
*.md
4-
PATENTS
5-
LICENSE
6-
Dockerfile
7-
.dockerignore
8-
.gitignore
9-
.travis.yml
10-
.istanbul.yml
11-
.git
12-
.github
13-
14-
# Build folder
15-
lib/
16-
17-
# Tests
18-
spec/
19-
20-
# IDEs
21-
.idea/
1+
node_modules
2+
npm-debug.log
3+
*.md
4+
PATENTS
5+
LICENSE
6+
Dockerfile
7+
.dockerignore
8+
.gitignore
9+
.travis.yml
10+
.istanbul.yml
11+
.git
12+
.github
13+
14+
# Build folder
15+
lib/
16+
17+
# Tests
18+
spec/
19+
20+
# IDEs
21+
.idea/

‎.editorconfig

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
1-
root = true
2-
3-
[*]
4-
indent_style = space
5-
indent_size = 2
6-
end_of_line = lf
7-
charset = utf-8
8-
trim_trailing_whitespace = true
9-
insert_final_newline = true
10-
11-
[*.md]
12-
trim_trailing_whitespace = false
1+
root = true
2+
3+
[*]
4+
indent_style = space
5+
indent_size = 2
6+
end_of_line = lf
7+
charset = utf-8
8+
trim_trailing_whitespace = true
9+
insert_final_newline = true
10+
11+
[*.md]
12+
trim_trailing_whitespace = false

‎.github/ISSUE_TEMPLATE/---1-report-an-issue.md

Lines changed: 55 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -1,55 +1,55 @@
1-
---
2-
name: "\U0001F41B Report an issue"
3-
about: A feature is not working as expected.
4-
title: ''
5-
labels: ''
6-
assignees: ''
7-
8-
---
9-
10-
### New Issue Checklist
11-
<!--
12-
Check every following box [x] before submitting your issue.
13-
Click the "Preview" tab for better readability.
14-
Thanks for contributing to Parse Platform!
15-
-->
16-
17-
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
18-
- [ ] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md).
19-
- [ ] I have searched through [existing issues](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
20-
- [ ] I can reproduce the issue with the latest versions of [Parse Server](https://github.com/parse-community/parse-server/releases) and [Parse Dashboard](https://github.com/parse-community/parse-dashboard/releases). <!-- We don't investigate issues for outdated releases. -->
21-
22-
### Issue Description
23-
<!-- What is the specific issue? -->
24-
25-
### Steps to reproduce
26-
<!-- How can someone else reproduce the issue? -->
27-
28-
### Actual Outcome
29-
<!-- What outcome did you get? -->
30-
31-
### Expected Outcome
32-
<!-- What outcome did you expect? -->
33-
34-
### Environment
35-
<!-- Be specific with versions, don't use "latest" or semver ranges like "~x.y.z" or "^x.y.z". -->
36-
37-
Dashboard
38-
- Parse Dashboard version: `FILL_THIS_OUT`
39-
- Browser (Safari, Chrome, Firefox, Edge, etc.): `FILL_THIS_OUT`
40-
- Browser version: `FILL_THIS_OUT`
41-
42-
Server
43-
- Parse Server version: `FILL_THIS_OUT`
44-
- Operating system: `FILL_THIS_OUT`
45-
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): `FILL_THIS_OUT`
46-
47-
Database
48-
- System (MongoDB or Postgres): `FILL_THIS_OUT`
49-
- Database version: `FILL_THIS_OUT`
50-
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): `FILL_THIS_OUT`
51-
52-
### Logs
53-
<!--
54-
Include relevant logs here. Turn on additional logging by configuring VERBOSE=1 in your environment. If you get a Browser JavaScript error run `npm run dev` to see source maps and a more detailed stack trace.
55-
-->
1+
---
2+
name: "\U0001F41B Report an issue"
3+
about: A feature is not working as expected.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### New Issue Checklist
11+
<!--
12+
Check every following box [x] before submitting your issue.
13+
Click the "Preview" tab for better readability.
14+
Thanks for contributing to Parse Platform!
15+
-->
16+
17+
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
18+
- [ ] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md).
19+
- [ ] I have searched through [existing issues](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
20+
- [ ] I can reproduce the issue with the latest versions of [Parse Server](https://github.com/parse-community/parse-server/releases) and [Parse Dashboard](https://github.com/parse-community/parse-dashboard/releases). <!-- We don't investigate issues for outdated releases. -->
21+
22+
### Issue Description
23+
<!-- What is the specific issue? -->
24+
25+
### Steps to reproduce
26+
<!-- How can someone else reproduce the issue? -->
27+
28+
### Actual Outcome
29+
<!-- What outcome did you get? -->
30+
31+
### Expected Outcome
32+
<!-- What outcome did you expect? -->
33+
34+
### Environment
35+
<!-- Be specific with versions, don't use "latest" or semver ranges like "~x.y.z" or "^x.y.z". -->
36+
37+
Dashboard
38+
- Parse Dashboard version: `FILL_THIS_OUT`
39+
- Browser (Safari, Chrome, Firefox, Edge, etc.): `FILL_THIS_OUT`
40+
- Browser version: `FILL_THIS_OUT`
41+
42+
Server
43+
- Parse Server version: `FILL_THIS_OUT`
44+
- Operating system: `FILL_THIS_OUT`
45+
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): `FILL_THIS_OUT`
46+
47+
Database
48+
- System (MongoDB or Postgres): `FILL_THIS_OUT`
49+
- Database version: `FILL_THIS_OUT`
50+
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): `FILL_THIS_OUT`
51+
52+
### Logs
53+
<!--
54+
Include relevant logs here. Turn on additional logging by configuring VERBOSE=1 in your environment. If you get a Browser JavaScript error run `npm run dev` to see source maps and a more detailed stack trace.
55+
-->

‎.github/ISSUE_TEMPLATE/---2-feature-request.md

Lines changed: 33 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,34 @@
1-
---
2-
name: "\U0001F4A1 Request a feature"
3-
about: Suggest new functionality or an enhancement of existing functionality.
4-
title: ''
5-
labels: ''
6-
assignees: ''
7-
8-
---
9-
10-
### New Feature / Enhancement Checklist
11-
<!--
12-
Check every following box [x] before submitting your issue.
13-
Click the "Preview" tab for better readability.
14-
Thanks for contributing to Parse Platform!
15-
-->
16-
17-
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
18-
- [ ] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md).
19-
- [ ] I have searched through [existing issues](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
20-
21-
### Current Limitation
22-
<!-- Which current limitation is the feature or enhancement addressing? -->
23-
24-
### Feature / Enhancement Description
25-
<!-- What is the concept of the functionality and how should it be implemented? -->
26-
27-
### Example Use Case
28-
<!-- What is an example use case in steps (1. / 2. / 3. / etc.) that describes the functionality? -->
29-
30-
### Alternatives / Workarounds
31-
<!-- Which alternatives or workarounds exist currently? -->
32-
33-
### 3rd Party References
1+
---
2+
name: "\U0001F4A1 Request a feature"
3+
about: Suggest new functionality or an enhancement of existing functionality.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### New Feature / Enhancement Checklist
11+
<!--
12+
Check every following box [x] before submitting your issue.
13+
Click the "Preview" tab for better readability.
14+
Thanks for contributing to Parse Platform!
15+
-->
16+
17+
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
18+
- [ ] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md).
19+
- [ ] I have searched through [existing issues](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
20+
21+
### Current Limitation
22+
<!-- Which current limitation is the feature or enhancement addressing? -->
23+
24+
### Feature / Enhancement Description
25+
<!-- What is the concept of the functionality and how should it be implemented? -->
26+
27+
### Example Use Case
28+
<!-- What is an example use case in steps (1. / 2. / 3. / etc.) that describes the functionality? -->
29+
30+
### Alternatives / Workarounds
31+
<!-- Which alternatives or workarounds exist currently? -->
32+
33+
### 3rd Party References
3434
<!-- Have you seen a similar functionality provided somewhere else? -->

‎.github/ISSUE_TEMPLATE/config.yml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
blank_issues_enabled: false
2-
contact_links:
3-
- name: 🙋🏽‍♀️ Getting help with code
4-
url: https://stackoverflow.com/questions/tagged/parse-platform
5-
about: Get help with code-level questions on Stack Overflow.
6-
- name: 🙋 Getting general help
7-
url: https://community.parseplatform.org
8-
about: Get help with other questions on our Community Forum.
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: 🙋🏽‍♀️ Getting help with code
4+
url: https://stackoverflow.com/questions/tagged/parse-platform
5+
about: Get help with code-level questions on Stack Overflow.
6+
- name: 🙋 Getting general help
7+
url: https://community.parseplatform.org
8+
about: Get help with other questions on our Community Forum.

‎.github/dependabot.yml

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
# Dependabot dependency updates
2-
# Docs: https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
3-
4-
version: 2
5-
updates:
6-
- package-ecosystem: "npm"
7-
# Location of package-lock.json
8-
directory: "/"
9-
# Check daily for updates
10-
schedule:
11-
interval: "daily"
12-
commit-message:
13-
# Set commit message prefix
14-
prefix: "refactor"
1+
# Dependabot dependency updates
2+
# Docs: https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
3+
4+
version: 2
5+
updates:
6+
- package-ecosystem: "npm"
7+
# Location of package-lock.json
8+
directory: "/"
9+
# Check daily for updates
10+
schedule:
11+
interval: "daily"
12+
commit-message:
13+
# Set commit message prefix
14+
prefix: "refactor"

‎.github/pull_request_template.md

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,26 @@
1-
### New Pull Request Checklist
2-
<!--
3-
Please check the following boxes [x] before submitting your issue.
4-
Click the "Preview" tab for better readability.
5-
Thanks for contributing to Parse Server!
6-
-->
7-
8-
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
9-
- [ ] I am creating this PR in reference to an [issue](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
10-
11-
### Issue Description
12-
<!-- Add a brief description of the issue this PR solves. -->
13-
14-
Closes: FILL_THIS_OUT
15-
16-
### Approach
17-
<!-- Add a description of the approach in this PR. -->
18-
19-
### TODOs before merging
20-
<!--
21-
Add TODOs that need to be completed before merging this PR.
22-
Delete TODOs that do not apply to this PR.
23-
-->
24-
25-
- [ ] Add tests
26-
- [ ] Add changes to documentation (guides, repository pages, in-code descriptions)
1+
### New Pull Request Checklist
2+
<!--
3+
Please check the following boxes [x] before submitting your issue.
4+
Click the "Preview" tab for better readability.
5+
Thanks for contributing to Parse Server!
6+
-->
7+
8+
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md).
9+
- [ ] I am creating this PR in reference to an [issue](https://github.com/parse-community/parse-dashboard/issues?q=is%3Aissue).
10+
11+
### Issue Description
12+
<!-- Add a brief description of the issue this PR solves. -->
13+
14+
Closes: FILL_THIS_OUT
15+
16+
### Approach
17+
<!-- Add a description of the approach in this PR. -->
18+
19+
### TODOs before merging
20+
<!--
21+
Add TODOs that need to be completed before merging this PR.
22+
Delete TODOs that do not apply to this PR.
23+
-->
24+
25+
- [ ] Add tests
26+
- [ ] Add changes to documentation (guides, repository pages, in-code descriptions)

0 commit comments

Comments
 (0)