qcobjects-cli 2.3.50 → 2.4.21

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.
Files changed (36) hide show
  1. package/.github/FUNDING.yml +12 -0
  2. package/.github/ISSUE_TEMPLATE/bug_report.md +38 -0
  3. package/.github/ISSUE_TEMPLATE/custom.md +10 -0
  4. package/.github/ISSUE_TEMPLATE/feature_request.md +20 -0
  5. package/.github/ISSUE_TEMPLATE/issue-template.md +33 -0
  6. package/.github/workflows/codeql-analysis.yml +71 -0
  7. package/.github/workflows/npmpublish-beta.yml +38 -0
  8. package/.github/workflows/npmpublish-lts.yml +38 -0
  9. package/.github/workflows/npmpublish-main.yml +38 -0
  10. package/.gitlab-ci.yml +3 -2
  11. package/VERSION +1 -1
  12. package/backend/com.qcobjects.backend.microservice.static.js +40 -24
  13. package/backend/org.qcobjects.backend.php.js +149 -116
  14. package/{org.quickcorp.qcobjects.cli.commands.jira.client_services.js → com.qcobjects.cli.commands.jira.client_services.js} +29 -22
  15. package/{org.quickcorp.qcobjects.cli.commands.jira.js → com.qcobjects.cli.commands.jira.js} +77 -60
  16. package/{org.quickcorp.qcobjects.cli.commands.js → com.qcobjects.cli.commands.js} +3 -3
  17. package/com.qcobjects.cli.commands.version.js +285 -0
  18. package/org.qcobjects.common.pipelog.js +55 -0
  19. package/org.qcobjects.enterprise.commands.js +149 -139
  20. package/org.quickcorp.qcobjects.api.client_services.js +31 -20
  21. package/org.quickcorp.qcobjects.cli.js +288 -275
  22. package/org.quickcorp.qcobjects.collab.server.js +317 -308
  23. package/org.quickcorp.qcobjects.defaultsettings.js +1 -1
  24. package/org.quickcorp.qcobjects.main.file.js +100 -79
  25. package/org.quickcorp.qcobjects.main.http.gae.server.js +264 -232
  26. package/org.quickcorp.qcobjects.main.http.server.js +155 -145
  27. package/org.quickcorp.qcobjects.main.http2.server.js +198 -191
  28. package/package.json +18 -10
  29. package/qcobjects-cli.js +8 -11
  30. package/qcobjects-collab.js +8 -6
  31. package/qcobjects-createcert.js +28 -16
  32. package/qcobjects-gae-http-server.js +8 -5
  33. package/qcobjects-http-server.js +7 -5
  34. package/qcobjects-http2-server.js +8 -5
  35. package/qcobjects-shell.js +113 -107
  36. package/org.quickcorp.qcobjects.cli.commands.version.js +0 -267
@@ -0,0 +1,12 @@
1
+ # These are supported funding model platforms
2
+
3
+ github: [jeanmachuca]
4
+ patreon: qcobjects # Replace with a single Patreon username
5
+ open_collective: # Replace with a single Open Collective username
6
+ ko_fi: # Replace with a single Ko-fi username
7
+ tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
8
+ community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
9
+ liberapay: # Replace with a single Liberapay username
10
+ issuehunt: # Replace with a single IssueHunt username
11
+ otechie: # Replace with a single Otechie username
12
+ custom: ['http://sponsorsignup.qcobjects.dev/'] # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']
@@ -0,0 +1,38 @@
1
+ ---
2
+ name: Bug report
3
+ about: Create a report to help us improve
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ **Describe the bug**
11
+ A clear and concise description of what the bug is.
12
+
13
+ **To Reproduce**
14
+ Steps to reproduce the behavior:
15
+ 1. Go to '...'
16
+ 2. Click on '....'
17
+ 3. Scroll down to '....'
18
+ 4. See error
19
+
20
+ **Expected behavior**
21
+ A clear and concise description of what you expected to happen.
22
+
23
+ **Screenshots**
24
+ If applicable, add screenshots to help explain your problem.
25
+
26
+ **Desktop (please complete the following information):**
27
+ - OS: [e.g. iOS]
28
+ - Browser [e.g. chrome, safari]
29
+ - Version [e.g. 22]
30
+
31
+ **Smartphone (please complete the following information):**
32
+ - Device: [e.g. iPhone6]
33
+ - OS: [e.g. iOS8.1]
34
+ - Browser [e.g. stock browser, safari]
35
+ - Version [e.g. 22]
36
+
37
+ **Additional context**
38
+ Add any other context about the problem here.
@@ -0,0 +1,10 @@
1
+ ---
2
+ name: Custom issue template
3
+ about: Describe this issue template's purpose here.
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+
@@ -0,0 +1,20 @@
1
+ ---
2
+ name: Feature request
3
+ about: Suggest an idea for this project
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ **Is your feature request related to a problem? Please describe.**
11
+ A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12
+
13
+ **Describe the solution you'd like**
14
+ A clear and concise description of what you want to happen.
15
+
16
+ **Describe alternatives you've considered**
17
+ A clear and concise description of any alternative solutions or features you've considered.
18
+
19
+ **Additional context**
20
+ Add any other context or screenshots about the feature request here.
@@ -0,0 +1,33 @@
1
+ ---
2
+ name: Issue template
3
+ about: QCObjects issue template
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ **Purpose:**
11
+ Name of your purpose or proposal
12
+ Example: Compliance with ECMA 262
13
+
14
+ **Feature:**
15
+ Feature (existing or new) that you want to affect with this issue.
16
+ Examples are: Nested components stack, dynamic components load. Dynamic complex cache control, etc.
17
+
18
+ **Artifact:**
19
+ The artifact that you are affecting, touching , involving with this issue .
20
+ Examples: Component Tag, Component Class, Controller, View, Effect, Import, Export, global scope... etc
21
+
22
+ **Priority:**
23
+ How concerned are you about this issue: High priority, low priority, middle priority. (Please no other values here)
24
+
25
+ **Changes:**
26
+ Please put here a piece of code you want to simplify or improve. You’re free to fork QCObjects for your own needs but I highly recommend you to spend some time standardizing. We review everything and test everything almost everywhere we can before to put in action a code change. And it’s because we want to make QCObjects a really professional tool, not just another “JavaScript something”. We want your projects to be listed in the best quality line lists. So please let us reject some proposals in order to make this happen.
27
+
28
+ -------
29
+
30
+ __Additional Information__
31
+ Issues will not be deleted unless they not meet the GitHub code of conduct.
32
+ All the issues will be answered as soon as possible.
33
+ Please try to read the issues first before to put a new one.
@@ -0,0 +1,71 @@
1
+ # For most projects, this workflow file will not need changing; you simply need
2
+ # to commit it to your repository.
3
+ #
4
+ # You may wish to alter this file to override the set of languages analyzed,
5
+ # or to provide custom queries or build logic.
6
+ #
7
+ # ******** NOTE ********
8
+ # We have attempted to detect the languages in your repository. Please check
9
+ # the `language` matrix defined below to confirm you have the correct set of
10
+ # supported CodeQL languages.
11
+ #
12
+ name: "CodeQL"
13
+
14
+ on:
15
+ push:
16
+ branches: [ main ]
17
+ pull_request:
18
+ # The branches below must be a subset of the branches above
19
+ branches: [ "v2.3", "v2.4" ]
20
+ schedule:
21
+ - cron: '23 16 * * 2'
22
+
23
+ jobs:
24
+ analyze:
25
+ name: Analyze
26
+ runs-on: ubuntu-latest
27
+ permissions:
28
+ actions: read
29
+ contents: read
30
+ security-events: write
31
+
32
+ strategy:
33
+ fail-fast: false
34
+ matrix:
35
+ language: [ 'javascript' ]
36
+ # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
37
+ # Learn more:
38
+ # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
39
+
40
+ steps:
41
+ - name: Checkout repository
42
+ uses: actions/checkout@v2
43
+
44
+ # Initializes the CodeQL tools for scanning.
45
+ - name: Initialize CodeQL
46
+ uses: github/codeql-action/init@v1
47
+ with:
48
+ languages: ${{ matrix.language }}
49
+ # If you wish to specify custom queries, you can do so here or in a config file.
50
+ # By default, queries listed here will override any specified in a config file.
51
+ # Prefix the list here with "+" to use these queries and those in the config file.
52
+ # queries: ./path/to/local/query, your-org/your-repo/queries@main
53
+
54
+ # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
55
+ # If this step fails, then you should remove it and run the build manually (see below)
56
+ - name: Autobuild
57
+ uses: github/codeql-action/autobuild@v1
58
+
59
+ # ℹ️ Command-line programs to run using the OS shell.
60
+ # 📚 https://git.io/JvXDl
61
+
62
+ # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
63
+ # and modify them (or add more) to build your code if your project
64
+ # uses a compiled language
65
+
66
+ #- run: |
67
+ # make bootstrap
68
+ # make release
69
+
70
+ - name: Perform CodeQL Analysis
71
+ uses: github/codeql-action/analyze@v1
@@ -0,0 +1,38 @@
1
+ # This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
2
+ # For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
3
+
4
+ name: Node.js Publish Beta version
5
+
6
+ on:
7
+ push:
8
+ branches:
9
+ - 'v*.*-beta'
10
+ tags:
11
+ - 'v*.*.*-beta'
12
+
13
+ jobs:
14
+ build:
15
+ runs-on: ubuntu-latest
16
+ steps:
17
+ - uses: actions/checkout@v3.3.0
18
+ - uses: actions/setup-node@v3.6.0
19
+ with:
20
+ node-version: 16
21
+ - run: npm ci
22
+ - run: npm test
23
+
24
+ publish-npm:
25
+ needs: build
26
+ runs-on: ubuntu-latest
27
+ steps:
28
+ - uses: actions/checkout@v3.3.0
29
+ - uses: actions/setup-node@v3.6.0
30
+ with:
31
+ node-version: 16
32
+ registry-url: https://registry.npmjs.org/
33
+ - name: Set up NPM authentication
34
+ run: echo "registry=https://registry.npmjs.org/:_authToken=${{secrets.NPM_TOKEN}}" >> ~/.npmrc
35
+ - run: npm ci
36
+ - run: npm publish --tag ${GITHUB_REF##*/}
37
+ env:
38
+ NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
@@ -0,0 +1,38 @@
1
+ # This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
2
+ # For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
3
+
4
+ name: Node.js Publish LTS version
5
+
6
+ on:
7
+ push:
8
+ branches:
9
+ - 'v*.*-lts'
10
+ tags:
11
+ - 'v*.*.*-lts'
12
+
13
+ jobs:
14
+ build:
15
+ runs-on: ubuntu-latest
16
+ steps:
17
+ - uses: actions/checkout@v3.3.0
18
+ - uses: actions/setup-node@v3.6.0
19
+ with:
20
+ node-version: 16
21
+ - run: npm ci
22
+ - run: npm test
23
+
24
+ publish-npm:
25
+ needs: build
26
+ runs-on: ubuntu-latest
27
+ steps:
28
+ - uses: actions/checkout@v3.3.0
29
+ - uses: actions/setup-node@v3.6.0
30
+ with:
31
+ node-version: 16
32
+ registry-url: https://registry.npmjs.org/
33
+ - name: Set up NPM authentication
34
+ run: echo "registry=https://registry.npmjs.org/:_authToken=${{secrets.NPM_TOKEN}}" >> ~/.npmrc
35
+ - run: npm ci
36
+ - run: npm publish --tag ${GITHUB_REF##*/}
37
+ env:
38
+ NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
@@ -0,0 +1,38 @@
1
+ # This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
2
+ # For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
3
+
4
+ name: Node.js Publish Package
5
+
6
+ on:
7
+ push:
8
+ branches:
9
+ - main
10
+ tags:
11
+ - 'v*.*.*'
12
+
13
+ jobs:
14
+ build:
15
+ runs-on: ubuntu-latest
16
+ steps:
17
+ - uses: actions/checkout@v3.3.0
18
+ - uses: actions/setup-node@v3.6.0
19
+ with:
20
+ node-version: 16
21
+ - run: npm ci
22
+ - run: npm test
23
+
24
+ publish-npm:
25
+ needs: build
26
+ runs-on: ubuntu-latest
27
+ steps:
28
+ - uses: actions/checkout@v3.3.0
29
+ - uses: actions/setup-node@v3.6.0
30
+ with:
31
+ node-version: 16
32
+ registry-url: https://registry.npmjs.org/
33
+ - name: Set up NPM authentication
34
+ run: echo "registry=https://registry.npmjs.org/:_authToken=${{secrets.NPM_TOKEN}}" >> ~/.npmrc
35
+ - run: npm ci
36
+ - run: npm publish
37
+ env:
38
+ NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
package/.gitlab-ci.yml CHANGED
@@ -10,6 +10,7 @@ deploy:
10
10
  changes:
11
11
  - package.json
12
12
  script:
13
- - echo "registry=https://registry.npmjs.org/:_authToken=${NPM_TOKEN}">.npmrc
13
+ - npm config set @scope:registry https://registry.npmjs.org/
14
+ - npm config set //registry.npmjs.org/:_authToken ${NPM_TOKEN}
14
15
  - npm ci
15
- - npm publish
16
+ # - npm publish --verbose
package/VERSION CHANGED
@@ -1 +1 @@
1
- 2.3.50
1
+ 2.4.21
@@ -36,9 +36,13 @@ const absolutePath = path.resolve(__dirname, "./");
36
36
  const mime = require("mime");
37
37
 
38
38
  Package("com.qcobjects.backend.microservice.static", [
39
- Class("Microservice", BackendMicroservice, {
40
- finishWithBody: function(stream) {},
41
- done: function() {
39
+ class Microservice extends BackendMicroservice {
40
+ constructor (){
41
+ super(...arguments);
42
+ }
43
+
44
+ finishWithBody (){}
45
+ done() {
42
46
  // read and send file content in the stream
43
47
 
44
48
  let microservice = this;
@@ -140,8 +144,9 @@ Package("com.qcobjects.backend.microservice.static", [
140
144
  sendFileLegacyHTTP(stream, fileName);
141
145
  }
142
146
 
143
- },
144
- static: function(method, data) {
147
+ }
148
+
149
+ static(method, data) {
145
150
  var microservice = this;
146
151
  var redirect_to = microservice.route.redirect_to;
147
152
  return new Promise(function(resolve, reject) {
@@ -178,69 +183,80 @@ Package("com.qcobjects.backend.microservice.static", [
178
183
  }
179
184
 
180
185
  });
181
- },
182
- head: function(formData) {
186
+ }
187
+
188
+ head(formData) {
183
189
  var microservice = this;
184
190
  microservice.static("head", formData).then(response => {
185
191
  microservice.body = response;
186
192
  microservice.done();
187
193
  });
188
- },
189
- get: function(formData) {
194
+ }
195
+
196
+ get(formData) {
190
197
  var microservice = this;
191
198
  microservice.static("get", formData).then(response => {
192
199
  microservice.body = response;
193
200
  microservice.done();
194
201
  });
195
- },
196
- post: function(formData) {
202
+ }
203
+
204
+ post(formData) {
197
205
  var microservice = this;
198
206
  microservice.static("post", formData).then(response => {
199
207
  microservice.body = response;
200
208
  microservice.done();
201
209
  });
202
- },
203
- put: function(formData) {
210
+ }
211
+
212
+ put(formData) {
204
213
  var microservice = this;
205
214
  microservice.static("put", formData).then(response => {
206
215
  microservice.body = response;
207
216
  microservice.done();
208
217
  });
209
- },
210
- delete: function(formData) {
218
+ }
219
+
220
+ delete(formData) {
211
221
  var microservice = this;
212
222
  microservice.static("delete", formData).then(response => {
213
223
  microservice.body = response;
214
224
  microservice.done();
215
225
  });
216
- },
217
- connect: function(formData) {
226
+ }
227
+
228
+ connect(formData) {
218
229
  var microservice = this;
219
230
  microservice.static("connect", formData).then(response => {
220
231
  microservice.body = response;
221
232
  microservice.done();
222
233
  });
223
- },
224
- options: function(formData) {
234
+ }
235
+
236
+ options(formData) {
225
237
  var microservice = this;
226
238
  microservice.static("options", formData).then(response => {
227
239
  microservice.body = response;
228
240
  microservice.done();
229
241
  });
230
- },
231
- trace: function(formData) {
242
+ }
243
+
244
+ trace(formData) {
232
245
  var microservice = this;
233
246
  microservice.static("trace", formData).then(response => {
234
247
  microservice.body = response;
235
248
  microservice.done();
236
249
  });
237
- },
238
- patch: function(formData) {
250
+ }
251
+
252
+ patch(formData) {
239
253
  var microservice = this;
240
254
  microservice.static("patch", formData).then(response => {
241
255
  microservice.body = response;
242
256
  microservice.done();
243
257
  });
244
258
  }
245
- })
259
+
260
+ }
261
+
246
262
  ]);