Skip to content

Update crucible-code-schema.json for crucible 0.1.5 - #6210

Open
NjoyimPeguy wants to merge 1 commit into
SchemaStore:masterfrom
NjoyimPeguy:crucible-code-0.1.5
Open

Update crucible-code-schema.json for crucible 0.1.5#6210
NjoyimPeguy wants to merge 1 commit into
SchemaStore:masterfrom
NjoyimPeguy:crucible-code-0.1.5

Conversation

@NjoyimPeguy

Copy link
Copy Markdown
Contributor

The served copy was last updated for crucible 0.1.2. This catches it up with
0.1.3 through 0.1.5, generated from the parser as always:

  • output.mouse — whether the wheel scrolls the terminal or the click places
    the cursor in the prompt.
  • updates.check — whether crucible asks GitHub which release is newest.
  • providers.<name>.baseUrl and providers.<name>.effort.
  • provider — which vendor to ask, by the name --model qualifies a model
    with.
  • Two descriptions corrected: the format is unstable for the whole 0.x line,
    and the keys a checked-in file is not read for now say so.

src/test/crucible-code-schema/config.json exercises the new blocks, and
src/negative_test/crucible-code-schema/not-a-rung.json covers the effort
enum. Prettier and node ./cli.js check --schema-name=crucible-code-schema.json
both run clean here.

Catches the served copy up with crucible 0.1.3 through 0.1.5: the output.mouse
and updates.check settings, per-provider baseUrl and effort, and the top-level
provider key that says which vendor to ask. The positive test exercises the new
blocks and a negative test covers the effort enum.
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the PR!

This section of the codebase is owned by @madskristensen and @hyperupcall - if they write a comment saying "LGTM" then it will be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant