JSONSchema for Pyrefly

[connernilsen]

We should add Pyrefly to jsonschema's schemastore to provide automatic structural validation for Pyrefly configs through their plugin. It's used by a lot of other type checkers as well, so seems like a good idea.

• Create a schema for Pyrefly (Add JSON schemas for pyrefly.toml and pyproject.toml validation #2100)
• Autogenerate Pyrefly schema with the schemars crate
• Make PR to upload Pyrefly schemas to schemastore

[connernilsen]

Hey @Prathamesh-tech-eng, if you're interested in continuing to work on this, I can add you as the assignee for this issue. Otherwise, let me know and I'll leave it open

[kinto0]

how does this differ from #536?

[connernilsen]

Oops forgot I made that one a while ago. We'll consider this one an expansion of the previous issue, since we're expanding the scope a bit and there's a lot of outdated discussion there

[Prathamesh-tech-eng]

Hey @connernilsen! I'd be interested in continuing work on this issue.

I see that Task 1 (creating the schemas) was completed in PR #2100. For the remaining tasks:

Task 2 - Autogenerate with schemars:**
The current schemas are manually maintained. I can work on:

• Adding schemars as a dependency to pyrefly_config
• Deriving JsonSchema on the config structs (ConfigBase, etc.)
• Creating a schema generation tool/binary that outputs to schemas/
• Integrating this into the build process or as a standalone command

Task 3 - SchemaStore submission:**
Once we have schemas hosted at https://pyrefly.org/schemas/, I can:

• Create a PR to SchemaStore following the guide in schemas/SCHEMASTORE.md
• Register both pyrefly.toml and pyproject.toml patterns in their catalog

Should I focus on Task 2 (schemars autogeneration) first?

[connernilsen]

@Prathamesh-tech-eng alright, I assigned you to the task. And yeah, could you work on task 2 first? That way, keeping schemastore in sync will be easier when we make changes.

Let me know if you have any questions or want to discuss anything around this.