In #23 we imported several pages from the old, pre-alpha site into new locations in the concept guide hierarchy. In all the pages imported in that issue's CL, the on-page code snippets were translated into {{{with code}}} blocks, to enable formatting of the content. Generally (I don't recall precisely) no other code-level changes were made.
The cue-lang/cue#2430 issue should be moved into cue-lang/docs-and-content, and should quickly have its changes incorporated so we're publishing code that compiles, even if it's not yet been modernised. That change should also move the page's code blocks to be script blocks, enabling automated tested of the published code .
This issue tracks the review of the resulting code on that page (after cue-lang/cue#2430 is resolved), and its modernisation.
In #23 we imported several pages from the old, pre-alpha site into new locations in the concept guide hierarchy. In all the pages imported in that issue's CL, the on-page code snippets were translated into
{{{with code}}}blocks, to enable formatting of the content. Generally (I don't recall precisely) no other code-level changes were made.Amongst the pages imported was https://cuelang.org/docs/concept/schema-definition-use-case/, which has an outstanding issue (cue-lang/cue#2430) which kindly mentions some fixes that could be made to the code to get it to compile.
The cue-lang/cue#2430 issue should be moved into
cue-lang/docs-and-content, and should quickly have its changes incorporated so we're publishing code that compiles, even if it's not yet been modernised. That change should also move the page'scodeblocks to bescriptblocks, enabling automated tested of the published code .This issue tracks the review of the resulting code on that page (after cue-lang/cue#2430 is resolved), and its modernisation.