@crowdin/app-project-module 0.50.0 → 0.51.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.
@@ -0,0 +1,4 @@
1
+ <script type="text/javascript">
2
+ window.opener.postMessage('{{{message}}}');
3
+ window.close();
4
+ </script>
@@ -0,0 +1,48 @@
1
+ <head>
2
+ <meta charset="UTF-8">
3
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
4
+ <meta http-equiv="X-UA-Compatible" content="ie=edge">
5
+ <title></title>
6
+ <link rel="stylesheet" href="/assets/css/styles.css">
7
+ <script type="module"
8
+ src="https://crowdin-web-components.s3.amazonaws.com/crowdin-web-components/crowdin-web-components.esm.js"></script>
9
+ <script nomodule=""
10
+ src="https://crowdin-web-components.s3.amazonaws.com/crowdin-web-components/crowdin-web-components.js"></script>
11
+ <script type="text/javascript" src="https://cdn.crowdin.com/apps/dist/iframe.js"></script>
12
+ <script type="text/javascript" src="/assets/js/polyfills/promise.js"></script>
13
+ <script type="text/javascript" src="/assets/js/polyfills/fetch.js"></script>
14
+ <script type="text/javascript" src="/assets/js/main.js"></script>
15
+ <script type="text/javascript" src="/assets/js/dependent.js"></script>
16
+ <style>
17
+ .ml-10 {
18
+ margin-left: 10px;
19
+ }
20
+ </style>
21
+ {{#if sentryData}}
22
+ <script
23
+ src="https://browser.sentry-cdn.com/7.60.0/bundle.replay.min.js"
24
+ integrity="sha384-N+VZps2PwFdv9LugkPA8nw+SMI1mGJG7IDe49jaxZlWDDJhHQ+SHakMpwhLQLAka"
25
+ crossorigin="anonymous"
26
+ ></script>
27
+ <script>
28
+ Sentry.init({
29
+ dsn: "{{sentryData.dsn}}",
30
+ environment: "frontend",
31
+ replaysSessionSampleRate: 0,
32
+ replaysOnErrorSampleRate: 1.0,
33
+ integrations: [new Sentry.Replay()],
34
+ });
35
+
36
+ Sentry.configureScope(function(scope) {
37
+ scope.setTag("identifier", "{{sentryData.appIdentifier}}");
38
+
39
+ AP.getContext(contextData => {
40
+ const { user_id, ...rest } = contextData;
41
+
42
+ user_id && scope.setUser({ id: user_id });
43
+ scope.setTags(rest);
44
+ });
45
+ });
46
+ </script>
47
+ {{/if}}
48
+ </head>
@@ -0,0 +1,26 @@
1
+ <!DOCTYPE html>
2
+ <html lang="en">
3
+
4
+ <head>
5
+ <meta charset="UTF-8">
6
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
7
+ <meta http-equiv="X-UA-Compatible" content="ie=edge">
8
+ <title></title>
9
+ <script type="module"
10
+ src="https://crowdin-web-components.s3.amazonaws.com/crowdin-web-components/crowdin-web-components.esm.js"></script>
11
+ <script nomodule=""
12
+ src="https://crowdin-web-components.s3.amazonaws.com/crowdin-web-components/crowdin-web-components.js"></script>
13
+ <script type="text/javascript" src="https://cdn.crowdin.com/apps/dist/iframe.js"></script>
14
+ </head>
15
+
16
+ <body>
17
+ <div class="i_w center">
18
+ <crowdin-alert type="warning">Subscribe to continue using the {{name}} app.</crowdin-alert>
19
+ <br/>
20
+ <crowdin-button primary onclick="window.open('{{subscribeLink}}','_blank')">Subscribe</crowdin-button>
21
+ <crowdin-button outlined onclick="window.open('https://crowdin.com/contacts','_blank')">Contact us
22
+ </crowdin-button>
23
+ </div>
24
+ </body>
25
+
26
+ </html>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@crowdin/app-project-module",
3
- "version": "0.50.0",
3
+ "version": "0.51.0",
4
4
  "description": "Module that generates for you all common endpoints for serving standalone Crowdin App",
5
5
  "main": "out/index.js",
6
6
  "types": "out/index.d.ts",
@@ -14,6 +14,9 @@
14
14
  "test-coverage": "jest --ci --reporters=jest-junit --reporters=default --coverage --coverageReporters=cobertura --coverageReporters=html",
15
15
  "test": "jest"
16
16
  },
17
+ "files": [
18
+ "out/**/*"
19
+ ],
17
20
  "dependencies": {
18
21
  "@aws-sdk/client-s3": "^3.540.0",
19
22
  "@aws-sdk/s3-request-presigner": "^3.484.0",
@@ -25,7 +28,7 @@
25
28
  "express": "4.19.2",
26
29
  "express-handlebars": "^5.3.5",
27
30
  "lodash.uniqby": "^4.7.0",
28
- "mysql2": "^3.9.4",
31
+ "mysql2": "^3.9.7",
29
32
  "node-cron": "^3.0.3",
30
33
  "pg": "^8.11.5",
31
34
  "redoc-express": "^2.1.0",
package/.release-it.json DELETED
@@ -1,17 +0,0 @@
1
- {
2
- "git": {
3
- "push": true,
4
- "commit": true,
5
- "commitMessage": "chore: version ${version} [skip ci]",
6
- "requireBranch": "master",
7
- "tag": true
8
- },
9
- "github": {
10
- "release": true,
11
- "autoGenerate": true,
12
- "releaseName": "${version}"
13
- },
14
- "npm": {
15
- "publish": false
16
- }
17
- }
@@ -1,76 +0,0 @@
1
- # Contributor Covenant Code of Conduct
2
-
3
- ## Our Pledge
4
-
5
- In the interest of fostering an open and welcoming environment, we as
6
- contributors and maintainers pledge to making participation in our project and
7
- our community a harassment-free experience for everyone, regardless of age, body
8
- size, disability, ethnicity, sex characteristics, gender identity and expression,
9
- level of experience, education, socio-economic status, nationality, personal
10
- appearance, race, religion, or sexual identity and orientation.
11
-
12
- ## Our Standards
13
-
14
- Examples of behavior that contributes to creating a positive environment
15
- include:
16
-
17
- * Using welcoming and inclusive language
18
- * Being respectful of differing viewpoints and experiences
19
- * Gracefully accepting constructive criticism
20
- * Focusing on what is best for the community
21
- * Showing empathy towards other community members
22
-
23
- Examples of unacceptable behavior by participants include:
24
-
25
- * The use of sexualized language or imagery and unwelcome sexual attention or
26
- advances
27
- * Trolling, insulting/derogatory comments, and personal or political attacks
28
- * Public or private harassment
29
- * Publishing others' private information, such as a physical or electronic
30
- address, without explicit permission
31
- * Other conduct which could reasonably be considered inappropriate in a
32
- professional setting
33
-
34
- ## Our Responsibilities
35
-
36
- Project maintainers are responsible for clarifying the standards of acceptable
37
- behavior and are expected to take appropriate and fair corrective action in
38
- response to any instances of unacceptable behavior.
39
-
40
- Project maintainers have the right and responsibility to remove, edit, or
41
- reject comments, commits, code, wiki edits, issues, and other contributions
42
- that are not aligned to this Code of Conduct, or to ban temporarily or
43
- permanently any contributor for other behaviors that they deem inappropriate,
44
- threatening, offensive, or harmful.
45
-
46
- ## Scope
47
-
48
- This Code of Conduct applies both within project spaces and in public spaces
49
- when an individual is representing the project or its community. Examples of
50
- representing a project or community include using an official project e-mail
51
- address, posting via an official social media account, or acting as an appointed
52
- representative at an online or offline event. Representation of a project may be
53
- further defined and clarified by project maintainers.
54
-
55
- ## Enforcement
56
-
57
- Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
- reported by contacting the project team at support@crowdin.com. All
59
- complaints will be reviewed and investigated and will result in a response that
60
- is deemed necessary and appropriate to the circumstances. The project team is
61
- obligated to maintain confidentiality with regard to the reporter of an incident.
62
- Further details of specific enforcement policies may be posted separately.
63
-
64
- Project maintainers who do not follow or enforce the Code of Conduct in good
65
- faith may face temporary or permanent repercussions as determined by other
66
- members of the project's leadership.
67
-
68
- ## Attribution
69
-
70
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
- available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72
-
73
- [homepage]: https://www.contributor-covenant.org
74
-
75
- For answers to common questions about this code of conduct, see
76
- https://www.contributor-covenant.org/faq
package/CONTRIBUTING.md DELETED
@@ -1,92 +0,0 @@
1
- # Contributing
2
-
3
- :tada: First off, thanks for taking the time to contribute! :tada:
4
-
5
- The following is a set of guidelines for contributing to Crowdin App Project module. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
6
-
7
- This project and everyone participating in it are governed by the [Code of Conduct](/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
8
-
9
- ## How can I contribute?
10
-
11
- ### Star this repo
12
-
13
- It's quick and goes a long way! :stars:
14
-
15
- ### Reporting Bugs
16
-
17
- This section guides you through submitting a bug report for Crowdin App Project module. Following these guidelines helps maintainers, and the community understand your report :pencil:, reproduce the behavior :computer:, and find related reports :mag_right:.
18
-
19
- When you are creating a bug report, please include as many details as possible.
20
-
21
- #### How Do I Submit a Bug Report?
22
-
23
- Bugs are tracked as [GitHub issues](https://github.com/crowdin/app-project-module/issues/).
24
-
25
- Explain the problem and include additional details to help reproduce the problem:
26
-
27
- * **Use a clear and descriptive title** for the issue to identify the problem.
28
- * **Describe the exact steps which reproduce the problem** in as many details as possible. Don't just say what you did, but explain how you did it.
29
- * **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
30
- * **Explain which behavior you expected to see instead and why.**
31
-
32
- Include details about your configuration and environment.
33
-
34
- ### Suggesting Enhancements
35
-
36
- This section guides you through submitting an enhancement suggestion for Crowdin App Project module, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion :pencil: and find related suggestions :mag_right:.
37
-
38
- When you are creating an enhancement suggestion, please include as many details as possible.
39
-
40
- #### How Do I Submit an Enhancement Suggestion?
41
-
42
- Enhancement suggestions are tracked as [GitHub issues](https://github.com/crowdin/app-project-module/issues/).
43
-
44
- Create an issue on that repository and provide the following information:
45
-
46
- * **Use a clear and descriptive title** for the issue to identify the suggestion.
47
- * **Provide a step-by-step description of the suggested enhancement** in as many details as possible.
48
- * **Describe the current behavior** and **explain which behavior you expected to see instead** and why.
49
- * **Explain why this enhancement would be useful** to most Crowdin App Project module users.
50
-
51
- ### Your First Code Contribution
52
-
53
- Unsure where to begin contributing to Crowdin App Project module? You can start by looking through these `good-first-issue` and `help-wanted` issues:
54
-
55
- * [Good first issue](https://github.com/crowdin/app-project-module/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) - issues which should only require a small amount of code, and a test or two.
56
- * [Help wanted](https://github.com/crowdin/app-project-module/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) - issues which should be a bit more involved than `Good first issue` issues.
57
-
58
- #### Pull Request Checklist
59
-
60
- Before sending your pull requests, make sure you followed the list below:
61
-
62
- - Read this guideline.
63
- - Read [Code of Conduct](/CODE_OF_CONDUCT.md).
64
- - Ensure that your code adheres to standard conventions, as used in the rest of the project.
65
- - Ensure that there are unit tests for your code.
66
- - Run unit tests.
67
-
68
- > **Note**
69
- > This project uses the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification for commit messages and PR titles.
70
-
71
- ##### Contributing to the docs
72
-
73
- First of all, you need to install Python (v3). Then install dependencies:
74
-
75
- ```bash
76
- pip install mkdocs
77
- pip install mkdocs-autorefs
78
- pip install mkdocs-material
79
- ```
80
-
81
- Run:
82
-
83
- ```bash
84
- mkdocs serve
85
- ```
86
-
87
- Visit http://127.0.0.1:8000/.
88
-
89
- #### Philosophy of code contribution
90
-
91
- - 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.
92
- - Bug fixes also generally require unit tests, because the presence of bugs usually indicates insufficient test coverage.