![]() Required fields add a “required field constraint”, denoted foo!: value, which is like foo?: value, but requires a regular field be provided for foo (a field foo: without !: or ?:). The main focus of the v0.6.0 release is the introduction of required fields.ĬUE already supports the “optional field constraint”, denoted foo?: value. ![]() This means that cue export now respects the -escape flag when set, and encoding/json only escapes HTML when HTMLEscape is used. The text at cue help injection explains how this in more detail.ĬL 552142 adds support for zero values in 64, which has the effect of fixing the error when attempting to use strconv.FormatFloat with a zero value.ĬL 548783 fixes a long-standing bug to make HTML escaping in JSON an opt-in. Thank you to and for contributing to this release!ĬL 543335 adds arch to set of injectable system variables understood by cue/load. Follow this link to learn more about Unity, install it, or get in touch with any questions. Adding your project to unity not only guarantees that we will not break your tests (if we do, we will work with you to fix your CUE code), but it also helps to improve the quality of each CUE release. unity continues to catch multiple issues with each release. unity is used to ensure that a project's CUE evaluations do not unexpectedly stop working, or regress in terms of performance. The main focus of this release is the introduction of required fields, as well as fixing a number of issues and regressions introduced in the v0.5.0 release.Īs a reminder: users can register their projects with unity, our regression and performance testing setup.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |