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.

Sign up for GitHub

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

Jump to bottom

Consider splitting Delve-specific objects in to their own schema #33

Open
rsek opened this issue May 28, 2024 · 0 comments
Open

Consider splitting Delve-specific objects in to their own schema #33

rsek opened this issue May 28, 2024 · 0 comments
Labels
💣 breaking A breaking change that will require a major release. 📐 schema Affects the JSON schema, which is the "source of truth" for Datasworn
Milestone
v0.2.0

Comments

@rsek
Copy link
Owner

rsek commented May 28, 2024

Ideally this can be genericized for use in all packages, so that people can expand on the existing schemas if their ruleset calls for it.

May overlap with #23
@rsek rsek changed the title Consider splitting Delve-specific objects in to their own schema, Consider splitting Delve-specific objects in to their own schema May 28, 2024
@rsek rsek added 💣 breaking A breaking change that will require a major release. 📐 schema Affects the JSON schema, which is the "source of truth" for Datasworn labels May 28, 2024
@rsek rsek modified the milestones: 1.0, v1.0, v0.2.0 Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💣 breaking A breaking change that will require a major release. 📐 schema Affects the JSON schema, which is the "source of truth" for Datasworn
Projects
None yet
Milestone
v0.2.0
Development

No branches or pull requests
1 participant
@rsek