Skip to content
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

Proposal B for JSON Schema generation #20

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Mearman
Copy link

@Mearman Mearman commented Mar 14, 2024

again for solving #10, built more conservatively based on the written spec

…pdates. Adjusted file associations in VSCode settings.
- Added a new TypeScript file `generate.ts` to handle the generation of JSON schema from a given TypeScript file. The script validates input parameters, generates a UUID, creates the schema configuration, and writes the resulting JSON schema to an output file.
…erfaces. Define properties and types for nodes and edges. Include descriptions for clarity. Create TypeScript interfaces for JsonCanvas, CanvasNode, TextNode, FileNode, LinkNode, GroupNode, AllNodes, and Edge with detailed attributes and types.

alternative proposal for obsidianmd#10
@Mearman Mearman changed the title Proposal A for JSON Schema generation Proposal B for JSON Schema generation Mar 15, 2024
@Mearman Mearman marked this pull request as draft March 15, 2024 15:46
@metruzanca
Copy link

I'm definitely a fan of B rather than A. Having typescript types/interfaces with sane names seems a lot more useful. This way not only do we get a JSON schema, we also get typescript types.

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.

2 participants