@crowdin/app-project-module 0.28.0-9 → 0.28.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CONTRIBUTING.md +1 -19
- package/README.md +984 -1
- package/out/handlers/crowdin-webhook.js +1 -1
- package/out/handlers/form-data-display.js +2 -6
- package/out/handlers/form-data-save.js +1 -5
- package/out/index.js +4 -13
- package/out/middlewares/render-ui-module.js +3 -5
- package/out/models/index.d.ts +10 -19
- package/out/static/js/form.js +1 -1
- package/out/util/cron.js +1 -5
- package/out/util/defaults.js +1 -5
- package/out/util/index.js +1 -5
- package/out/util/webhooks.js +4 -15
- package/out/views/form.handlebars +2 -4
- package/package.json +15 -15
- package/rollup.config.mjs +31 -0
package/CONTRIBUTING.md
CHANGED
|
@@ -59,30 +59,12 @@ Unsure where to begin contributing to Crowdin App Project module? You can start
|
|
|
59
59
|
|
|
60
60
|
Before sending your pull requests, make sure you followed the list below:
|
|
61
61
|
|
|
62
|
-
- Read this
|
|
62
|
+
- Read this guidelines.
|
|
63
63
|
- Read [Code of Conduct](/CODE_OF_CONDUCT.md).
|
|
64
64
|
- Ensure that your code adheres to standard conventions, as used in the rest of the project.
|
|
65
65
|
- Ensure that there are unit tests for your code.
|
|
66
66
|
- Run unit tests.
|
|
67
67
|
|
|
68
|
-
##### Contributing to the docs
|
|
69
|
-
|
|
70
|
-
First of all, you need to install Python (v3). Then install dependencies:
|
|
71
|
-
|
|
72
|
-
```bash
|
|
73
|
-
pip install mkdocs
|
|
74
|
-
pip install mkdocs-autorefs
|
|
75
|
-
pip install mkdocs-material
|
|
76
|
-
```
|
|
77
|
-
|
|
78
|
-
Run:
|
|
79
|
-
|
|
80
|
-
```bash
|
|
81
|
-
mkdocs serve
|
|
82
|
-
```
|
|
83
|
-
|
|
84
|
-
Visit http://127.0.0.1:8000/.
|
|
85
|
-
|
|
86
68
|
#### Philosophy of code contribution
|
|
87
69
|
|
|
88
70
|
- Include unit tests when you contribute new features, as they help to a) prove that your code works correctly, and b) guard against future breaking changes to lower the maintenance cost.
|