chofex-cli 0.1.202 → 0.1.206
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 +45 -40
- package/dist/index.js +499 -359
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,57 +14,56 @@ Instala uno de los dos paquetes.
|
|
|
14
14
|
|
|
15
15
|
```sh
|
|
16
16
|
andes register
|
|
17
|
-
chofex register
|
|
18
17
|
```
|
|
19
18
|
|
|
20
19
|
Para instalarlo dentro de un proyecto, usa `npm install hacktheandes-cli` y
|
|
21
|
-
ejecuta `npx andes register
|
|
20
|
+
ejecuta `npx andes register`.
|
|
22
21
|
|
|
23
|
-
|
|
22
|
+
El comando recomendado es `andes`. `chofex` sigue disponible por compatibilidad.
|
|
24
23
|
|
|
25
24
|
```sh
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
25
|
+
andes
|
|
26
|
+
andes whoami
|
|
27
|
+
andes update
|
|
28
|
+
andes upgrade
|
|
29
|
+
andes register
|
|
30
|
+
andes status
|
|
31
|
+
andes requirements
|
|
32
|
+
andes challenge list
|
|
33
|
+
andes challenge query --challenge black-box
|
|
34
|
+
andes challenge notebook --challenge black-box
|
|
35
|
+
andes challenge test --challenge black-box --source ./shipping.js
|
|
36
|
+
andes challenge evaluate --challenge black-box --source ./shipping.js
|
|
37
|
+
andes challenge ranking --challenge black-box
|
|
38
|
+
andes challenge init --challenge broken-agent
|
|
40
39
|
cd broken-agent && npm test
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
40
|
+
andes challenge test --challenge broken-agent --source ./scheduler.js
|
|
41
|
+
andes challenge evaluate --challenge broken-agent --source ./scheduler.js --review ./review.json
|
|
42
|
+
andes challenge ranking --challenge broken-agent
|
|
43
|
+
andes confirm
|
|
44
|
+
andes badge
|
|
45
|
+
andes badge regenerate
|
|
47
46
|
```
|
|
48
47
|
|
|
49
|
-
`
|
|
48
|
+
`andes update` and `andes upgrade` are interchangeable; both update the CLI
|
|
50
49
|
to the latest published version.
|
|
51
50
|
|
|
52
51
|
Las actualizaciones conservan el paquete instalado: `hacktheandes-cli` o
|
|
53
52
|
`chofex-cli`, independientemente del comando que uses.
|
|
54
53
|
|
|
55
|
-
Las copias instaladas también consultan npm cada vez que se inicia `
|
|
54
|
+
Las copias instaladas también consultan npm cada vez que se inicia `andes` e
|
|
56
55
|
instalan una versión publicada más reciente antes de ejecutar el comando. Si
|
|
57
56
|
npm o la red no están disponibles temporalmente, se continúa con la versión
|
|
58
57
|
actual. Usa `CHOFEX_AUTO_UPDATE=0` para desactivar esta comprobación.
|
|
59
58
|
|
|
60
|
-
`
|
|
59
|
+
`andes register` collects and submits an application with full name, role,
|
|
61
60
|
optional phone number, bio, portfolio URL, shipped project, LinkedIn and GitHub
|
|
62
61
|
URLs, and Terms and Conditions. Use `--input` to submit a completed JSON
|
|
63
62
|
application.
|
|
64
63
|
Acceptance creates a default badge from the Clerk profile visible to reviewers.
|
|
65
|
-
`
|
|
64
|
+
`andes confirm` updates the public name, one-line description, and picture
|
|
66
65
|
while separately collecting the legal full name and venue details required for attendance. After confirmation,
|
|
67
|
-
`
|
|
66
|
+
`andes badge regenerate` can also update those public fields and the QR
|
|
68
67
|
destination without changing the submitted application.
|
|
69
68
|
The technical challenges do not block application submission, but they are
|
|
70
69
|
mandatory for admission. An application does not reserve a seat; organizers
|
|
@@ -75,32 +74,38 @@ version; legacy attempts do not count toward admission.
|
|
|
75
74
|
|
|
76
75
|
The public ranking is read-only at `https://hacktheandes.com/challenges`.
|
|
77
76
|
|
|
78
|
-
Run `
|
|
79
|
-
|
|
77
|
+
Run `andes` to see your current progress and the next command to run.
|
|
78
|
+
`andes challenge` also checks your application before showing the challenge guide.
|
|
79
|
+
Repeating `andes register` after submission shows your next step without submitting again.
|
|
80
|
+
After acceptance, run `andes confirm`; after confirmation, run `andes badge`.
|
|
81
|
+
Confirmation generates the badge automatically. Repeat `andes badge` if it is still processing.
|
|
82
|
+
Run `andes --help` for the full command reference. The welcome screen's
|
|
80
83
|
landscape uses colored terminal cells, with readable text that works with your
|
|
81
84
|
terminal's line spacing. It adapts to the terminal width and has a plain ASCII
|
|
82
85
|
fallback when color is disabled with `NO_COLOR`. JSON output and individual
|
|
83
86
|
command results omit the welcome screen.
|
|
84
87
|
|
|
85
|
-
For agent or script input, `
|
|
86
|
-
`
|
|
88
|
+
For agent or script input, `andes schema --stage application` and
|
|
89
|
+
`andes schema --stage acceptance` print complete templates containing every
|
|
87
90
|
accepted JSON key. Validate a completed input file locally before submitting it:
|
|
88
91
|
|
|
89
92
|
```sh
|
|
90
|
-
|
|
93
|
+
andes --output json validate --stage application --input application.json
|
|
91
94
|
```
|
|
92
95
|
|
|
93
96
|
Validation does not contact the API, and a successful result does not echo input
|
|
94
97
|
values. Local validation errors include `acceptedFields` in JSON mode. The
|
|
95
98
|
`status` response already includes both the registration and its requirements;
|
|
96
99
|
use `requirements` only when requirements-only human output is preferred.
|
|
100
|
+
The CLI adds `data.nextStep` with `kind`, `message`, and `command` to registration
|
|
101
|
+
results and to home and challenge guidance. JSON output remains one versioned envelope.
|
|
97
102
|
|
|
98
|
-
Run `
|
|
103
|
+
Run `andes login` to authenticate. For automation, provide an OAuth access
|
|
99
104
|
token with `CHOFEX_TOKEN`.
|
|
100
105
|
|
|
101
106
|
### Authentication troubleshooting
|
|
102
107
|
|
|
103
|
-
If `
|
|
108
|
+
If `andes login` succeeds but `whoami` or an authenticated challenge command
|
|
104
109
|
returns `AUTHENTICATION_REQUIRED`, first remove any token or API URL overrides
|
|
105
110
|
from the shell. In Bash or Zsh:
|
|
106
111
|
|
|
@@ -117,7 +122,7 @@ Remove-Item Env:CHOFEX_TOKEN, Env:CHOFEX_API_URL -ErrorAction SilentlyContinue
|
|
|
117
122
|
Update by repeating the installation method you originally used. For npm:
|
|
118
123
|
|
|
119
124
|
```sh
|
|
120
|
-
npm install --global
|
|
125
|
+
npm install --global hacktheandes-cli@latest
|
|
121
126
|
```
|
|
122
127
|
|
|
123
128
|
For the standalone installer:
|
|
@@ -129,10 +134,10 @@ curl -fsSL https://hacktheandes.com/install | bash
|
|
|
129
134
|
Then renew the stored session and verify it:
|
|
130
135
|
|
|
131
136
|
```sh
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
137
|
+
andes --version
|
|
138
|
+
andes logout
|
|
139
|
+
andes login
|
|
140
|
+
andes --output json whoami
|
|
136
141
|
```
|
|
137
142
|
|
|
138
143
|
Versions before `0.1.140` used a retired API origin whose cross-origin redirect
|