|
3 | 3 |
|
4 | 4 | Available through https://crates.io/crates/typeql. |
5 | 5 | ``` |
6 | | -cargo add typeql@3.7.0 |
| 6 | +cargo add typeql@3.8.0-rc0 |
7 | 7 | ``` |
8 | 8 |
|
9 | 9 |
|
10 | 10 | ## New Features |
11 | | -- **Try blocks in write stages** |
| 11 | +- **Add built-in functions iid() and label()** |
12 | 12 |
|
13 | | - We allow `try {}` blocks in all write stages, viz. `insert`, `delete`, `put`, and `update`. |
| 13 | + We add `iid()` and `label()` to the built-in functions in the TypeQL grammar. |
14 | 14 |
|
15 | 15 |
|
16 | 16 |
|
17 | 17 | ## Bugs Fixed |
18 | | - |
| 18 | +- **Use XID_START and XID_CONTINUE character classes** |
| 19 | + |
| 20 | + We use `XID_START` and `XID_CONTINUE` character classes provided by pest instead of manually listing unicode codepoint ranges for our identifiers. We also change the definition of the word boundary (`WB`) to be "any character that is not an identifier continuation character" that resolves parsing bugs such as `let $var= 4;` failing to parse: `=` is not `PUNCTUATION`, so not valid word boundary. |
| 21 | + |
| 22 | + |
19 | 23 |
|
20 | 24 | ## Code Refactors |
21 | 25 |
|
22 | 26 |
|
23 | | -## Other Improvements |
24 | | - |
25 | | -- **Change CODEOWNERS** |
| 27 | +## Other Improvements |
| 28 | +- **Expose value parser** |
| 29 | + |
| 30 | + We expose value parsing as a top-level function, and update the value literal definitions. This lets us re-use the value parser for test frameworks in other repositories. |
| 31 | + |
| 32 | + |
| 33 | +- **Update TypeQL banner image link in README** |
26 | 34 |
|
27 | | -- **Fix illegal grammar error formatting** |
| 35 | +- **Add contributing guidelines to CONTRIBUTING.md** |
| 36 | + |
| 37 | +- **Allow trailing commas (#421)** |
| 38 | + |
| 39 | + To simplify writing and generating queries, we allow trailing commas anywhere we use a comma separated list of variables, statements, reductions, etc. |
| 40 | + |
28 | 41 |
|
29 | | - We fix the (internal) illegal grammar error formatting to show the part of the query that caused the error rather than the corresponding parsed subtree. |
| 42 | +- **Remove discussion and Stack Overflow links** |
| 43 | + |
| 44 | +- **Allow trailing commas** |
| 45 | + |
| 46 | + To simplify writing and generating queries, we allow trailing commas anywhere we use a comma separated list of variables, statements, reductions, etc. |
30 | 47 |
|
| 48 | + |
| 49 | + |
0 commit comments