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

chore: mechanism to update the validation schema if one of the structures changes #527

Open
mike-winberry opened this issue Jul 9, 2024 · 0 comments
Open

chore: mechanism to update the validation schema if one of the structures changes #527

mike-winberry opened this issue Jul 9, 2024 · 0 comments
Labels
question Further information is requested

Comments

@mike-winberry
Copy link
Contributor

mike-winberry commented Jul 9, 2024 •
edited
Loading

Description

What is the mechanism to update the schema if one of the structures changes? Is that something that we should add as like a make target to hit in CI?

Originally posted by @meganwolf0 in #473 (comment)

Investigate the potential processes to ensure the validation schema and all future schemas flag when there are type changes and not schema changes.

Ideas:

  • ...
@github-actions github-actions bot added the triage Awaiting triage from the team label Jul 9, 2024
@mike-winberry mike-winberry changed the title chore: mechanism to update the validation schema if one of the structures changes? Is that something that we should add as like a make target to hit in CI chore: mechanism to update the validation schema if one of the structures changes Jul 9, 2024
@mike-winberry mike-winberry mentioned this issue Jul 9, 2024
Merged
12 tasks
@brandtkeller brandtkeller added question Further information is requested and removed triage Awaiting triage from the team labels Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
Lula and Friends
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brandtkeller @mike-winberry