@jutge.org/toolkit 4.2.25 → 4.2.27

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.
@@ -319,7 +319,7 @@ Test cases are used to evaluate the correctness of user submissions. Each test c
319
319
 
320
320
  In addition, `test` can also make use of a `test.ops` file to describe some low-level advanced options for its correction.
321
321
 
322
- Test case names should be made of letters, digits, dashes, and underscores. Do not use special characters or blanks in them. Test cases whose name starts with `sample`, `public`, `hint`, or `distilled` have a special meaning and are considered public (might be seen by users). It is common to name test cases with names such as `sample-1`, `sample-2`, or `test-hard`.
322
+ Test case names should be made of letters, digits, dashes, and underscores. Do not use special characters or blanks in them. Test cases whose name contain `sample` or starts with `public`, `hint`, or `distilled` have a special meaning and are considered public (might be seen by users). It is common to name test cases with names such as `sample-1`, `sample-2`, or `test-hard`.
323
323
 
324
324
  At correction time, public test cases are corrected before the private ones. The cases are processed sequentially, ordered by their name.
325
325
 
@@ -335,7 +335,7 @@ In addition, there must be no spaces before a line break. In particular, there m
335
335
 
336
336
  ### Sample test cases
337
337
 
338
- Sample test cases start with `sample` and will be revealed to users in the problem statement. As such, they should make clear the format of the input and the output for the problem and should be reasonably short.
338
+ Sample test cases that contain `sample` in their filename and will be revealed to users in the problem statement. As such, they should make clear the format of the input and the output for the problem and should be reasonably short.
339
339
 
340
340
  ### Public test cases
341
341
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@jutge.org/toolkit",
3
3
  "description": "Toolkit to prepare problems for Jutge.org",
4
- "version": "4.2.25",
4
+ "version": "4.2.27",
5
5
  "homepage": "https://jutge.org",
6
6
  "author": {
7
7
  "name": "Jutge.org",
@@ -27,7 +27,7 @@
27
27
  ],
28
28
  "repository": {
29
29
  "type": "git",
30
- "url": "git+https://github.com/jutge-org/new-jutge-toolkit.git"
30
+ "url": "git+https://github.com/jutge-org/jutge-toolkit.git"
31
31
  },
32
32
  "keywords": [
33
33
  "jutge.org",