-
Notifications
You must be signed in to change notification settings - Fork 55
Validate project files, add order, insert version #116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
0045db8
d103e26
e8efedb
a26fc2d
c297922
a923be0
b6bb4f3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| { | ||
| "name": "Latest Mathlib", | ||
| "name": "_LeanVers_ with Mathlib", | ||
| "default": true, | ||
| "hidden": false, | ||
| "examples": [ | ||
|
|
||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what's these day the recommended way of automatically follow stable releases? the file
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For live.lean-lang.org, we're currently getting the stable release by following the cslib But this doesn't work for "latest release" where there's no corresponding tag in mathlib or cslib, and it doesn't work as soon as you want to say "I want the latest stable release where there's a version of cslib, and lean4export, and comparator"... which is also something I want. So I'm planning on doing something a bit more complicated, I can try upstreaming if it would be helpful because there's not currently a great answer here.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ok that sounds even hackier indeed. I'm going to revert that for this PR, but I'd be happy to have a look at that in another PR seperately. Ideally |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| leanprover/lean4:stable | ||
| leanprover/lean4:v4.29.0 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| { | ||
| "name": "Stable Lean", | ||
| "name": "_LeanVers_", | ||
| "hidden": false | ||
| } |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| import { z } from "zod"; | ||
|
|
||
| export const zLeanWebExample = z.object({ | ||
| file: z.string(), | ||
| name: z.string(), | ||
| }); | ||
|
|
||
| export const zLeanWebProjectConfig = z.object({ | ||
| name: z.string(), | ||
| hidden: z.boolean().optional(), | ||
| default: z.boolean().optional(), | ||
| sortOrder: z.number().min(0).optional(), | ||
| examples: z.array(zLeanWebExample).optional(), | ||
| }); |
Uh oh!
There was an error while loading. Please reload this page.