@devkong/cli-nx 0.0.1 → 0.0.3

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/README.md CHANGED
@@ -9,20 +9,3 @@ Run `nx build kong-cli-nx` to build the library.
9
9
  ## Running unit tests
10
10
 
11
11
  Run `nx test kong-cli-nx` to execute the unit tests via [Jest](https://jestjs.io).
12
-
13
- ## Publishing
14
-
15
- Ensure that necessary package versions are bumped and that `~/.npmrc` contains:
16
-
17
- ```
18
- @kong:registry=https://nexus.shared.app-dts.net/repository/npm-hosted/
19
- //nexus.shared.app-dts.net/repository/npm-hosted/:username=kong
20
- //nexus.shared.app-dts.net/repository/npm-hosted/:_password=BASE_64_PASSWORD
21
- //nexus.shared.app-dts.net/repository/npm-hosted/:always-auth=true
22
- ```
23
-
24
- Than run next command:
25
-
26
- ```sh
27
- npx nx release publish --git-commit=false
28
- ```
package/package.json CHANGED
@@ -1,10 +1,6 @@
1
1
  {
2
2
  "name": "@devkong/cli-nx",
3
- "version": "0.0.1",
4
- "dependencies": {
5
- "@nx/devkit": "19.6.2",
6
- "tslib": "2.7.0"
7
- },
3
+ "version": "0.0.3",
8
4
  "type": "commonjs",
9
5
  "main": "./src/index.js",
10
6
  "typings": "./src/index.d.ts",
@@ -42,7 +42,7 @@ This will build the extension and tags it with the next available version. If it
42
42
 
43
43
  ### Assign an Alias to a Version
44
44
 
45
- You can assign an alias (like stable or latest) to a particular version. This alias will accessible in the UI as a separate step in workflow. For example, to assign the alias stable to version 1, use the following command:
45
+ You can assign an alias(good names: `stable`, `beta`) to a particular version. This alias will accessible in the UI as a separate step in workflow. For example, to assign the alias stable to version 1, use the following command:
46
46
 
47
47
  ```shell script
48
48
  kong set-alias stable 1
@@ -41,7 +41,7 @@ class InputData(BaseModel):
41
41
  class OutputData(BaseModel):
42
42
  # Define the structure of the output data that your extension will return.
43
43
 
44
- value: str = Field(examples=["Value from the string_field"])
44
+ value: str = Field(examples=["Hello"], description="Value from the string_field")
45
45
 
46
46
 
47
47
  class ExtensionTemplate(KongFunction):
@@ -62,4 +62,4 @@ app = App(
62
62
  )
63
63
 
64
64
  if __name__ == "__main__":
65
- app.run(sys.argv)
65
+ app.run(sys.argv)
@@ -1,21 +0,0 @@
1
- @echo off
2
-
3
- where python >nul 2>&1
4
- if %errorlevel% equ 0 (
5
- set PYTHON_CMD=python
6
- ) else (
7
- set PYTHON_CMD=python3
8
- )
9
-
10
- where pip >nul 2>&1
11
- if %errorlevel% equ 0 (
12
- set PIP_CMD=pip
13
- ) else (
14
- set PIP_CMD=pip3
15
- )
16
-
17
- %PYTHON_CMD% -m venv .venv
18
-
19
- call .venv\Scripts\activate
20
-
21
- %PIP_CMD% install -r requirements-dev.txt -r requirements.txt
@@ -1,19 +0,0 @@
1
- #!/bin/bash
2
-
3
- if [ -x "$(command -v python)" ]; then
4
- PYTHON_CMD="python"
5
- else
6
- PYTHON_CMD="python3"
7
- fi
8
-
9
- if [ -x "$(command -v python)" ]; then
10
- PIP_CMD="pip"
11
- else
12
- PIP_CMD="pip3"
13
- fi
14
-
15
- $PYTHON_CMD -m venv .venv
16
-
17
- source activate
18
-
19
- $PIP_CMD install -r requirements-dev.txt -r requirements.txt