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

Clarify joinSchema relation to a lineage's schemas: & or must()? #76

Open
sdboyer opened this issue Oct 20, 2022 · 1 comment
Open

Clarify joinSchema relation to a lineage's schemas: & or must()? #76

sdboyer opened this issue Oct 20, 2022 · 1 comment
Assignees

Comments

@sdboyer
Copy link
Contributor

sdboyer commented Oct 20, 2022

Currently, #Lineage.joinSchema is unified with all schemas in a lineage. Sometimes that's desirable. Other times, i think what we want is really something more like a must()/constraint.

These should probably be teased out into two distinct capabilities.

@frossano-grafana
Copy link

make users write that they don't have default panel options instead assuming that when there is nothing the defaul is null
the net effect is the same, the change is in ergonomic of using Thema

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

No branches or pull requests

2 participants