@jutge.org/toolkit 4.2.38 → 4.3.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/README.md +15 -4
- package/dist/index.js +484 -420
- package/docs/getting-started-guide.md +1 -0
- package/docs/login.md +1 -0
- package/docs/windows.md +106 -0
- package/package.json +2 -1
- package/toolkit/ai.ts +56 -0
- package/toolkit/generate.ts +30 -13
- package/toolkit/index.ts +2 -0
- package/toolkit/submit.ts +14 -0
package/README.md
CHANGED
|
@@ -60,11 +60,14 @@ jtk generate problem
|
|
|
60
60
|
cd my-problem.pbm
|
|
61
61
|
jtk make
|
|
62
62
|
|
|
63
|
-
# Verify a solution
|
|
64
|
-
jtk verify
|
|
63
|
+
# Verify a solution (locally)
|
|
64
|
+
jtk verify candidate.py
|
|
65
65
|
|
|
66
66
|
# Upload to Jutge.org
|
|
67
67
|
jtk upload
|
|
68
|
+
|
|
69
|
+
# Submit a solution to Jutge.org
|
|
70
|
+
jtk submit candidate.py
|
|
68
71
|
```
|
|
69
72
|
|
|
70
73
|
For a complete walkthrough, see the [Getting Started Guide](docs/getting-started-guide.md).
|
|
@@ -85,8 +88,8 @@ For a complete walkthrough, see the [Getting Started Guide](docs/getting-started
|
|
|
85
88
|
3. Build the problem
|
|
86
89
|
- Run `jtk make` to build all problem elements (statements, solutions, correct test cases)
|
|
87
90
|
|
|
88
|
-
4. Optional:
|
|
89
|
-
- Use `jtk verify <solution>` to test
|
|
91
|
+
4. Optional: Locally verify candidate solutions
|
|
92
|
+
- Use `jtk verify <solution>` to test candidate solutions for correctness
|
|
90
93
|
|
|
91
94
|
5. Optional: Stage the problem
|
|
92
95
|
- Run `jtk stage` to stage the files as will be used by Jutge.org
|
|
@@ -96,6 +99,11 @@ For a complete walkthrough, see the [Getting Started Guide](docs/getting-started
|
|
|
96
99
|
|
|
97
100
|
Remember that Jutge.org does not generate the correct test cases; you must provide them.
|
|
98
101
|
|
|
102
|
+
7. Optional: Test a candidate solution by submitting it to Jutge.org
|
|
103
|
+
- Use `jtk submit -l <language> <solution>` to submit the solution to Jutge.org in a specific language
|
|
104
|
+
|
|
105
|
+
In order to submit a candidate solution, you need to have the problem uploaded to Jutge.org. This solution will be judged by Jutge.org and you will get its verdict.
|
|
106
|
+
|
|
99
107
|
## Documentation
|
|
100
108
|
|
|
101
109
|
### Essential Guides
|
|
@@ -136,6 +144,9 @@ jtk stage # Stage problem for Jutge.org
|
|
|
136
144
|
# Publishing
|
|
137
145
|
jtk upload # Upload problem to Jutge.org
|
|
138
146
|
|
|
147
|
+
# Testing
|
|
148
|
+
jtk submit -l en candidate.py # Submit a candidate solution to Jutge.org
|
|
149
|
+
|
|
139
150
|
# Passcode management
|
|
140
151
|
jtk passcode show # Show the passcode of the problem
|
|
141
152
|
jtk passcode set # Set the passcode of the problem
|