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

re_datastore: schema registry / runtime payload validation #447

Closed
teh-cmc opened this issue Dec 2, 2022 · 1 comment
Closed

re_datastore: schema registry / runtime payload validation #447

teh-cmc opened this issue Dec 2, 2022 · 1 comment
Labels
🏹 arrow concerning arrow ⛃ re_datastore affects the datastore itself

Comments

@teh-cmc
Copy link
Member

teh-cmc commented Dec 2, 2022 •
edited
Loading

Schema registry / runtime payload validation

First we need to ask ourselves: do we want actually want this? Do we want to stay fully dynamic? Do we want to be a just a little bit strict? Where do we draw the line? etc

See also #435 .

  • builtin components
  • opening the registration process to user-defined components.
@teh-cmc teh-cmc added 🏹 arrow concerning arrow ⛃ re_datastore affects the datastore itself labels Dec 2, 2022
@teh-cmc
Copy link
Member Author

teh-cmc commented Apr 18, 2023

At this point this is pretty much superseded by component vs. datatypes RFC and #1882

@teh-cmc teh-cmc closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🏹 arrow concerning arrow ⛃ re_datastore affects the datastore itself
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@teh-cmc