-
-
Notifications
You must be signed in to change notification settings - Fork 715
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
Ship with spec validation interceptor #515
Comments
Spec is still in alpha, I don't think anyone outside of Cognitect has a good idea of where it's going to end up. I'm pretty hesitant to put anything core to spec in re-frame at the moment. I'm a little bit worried about the upgrade path, and how we might have to support multiple versions in re-frame, error message formatting, and perhaps picking the wrong abstractions. re-frame is very flexible, so you can add these kinds of things yourself. If you make one we'd be happy to add it to the re-frame resources. |
@urzds as @danielcompton says we look forward to officially integrating spec when it becomes stable but without a known timeline for that, I'm going to close this issue for now. |
What about Plumatic Schema as an alternative? |
@urzds
|
It would be nice if re-frame could bring a few more batteries, like a spec validation interceptor for the application state (i.e.
:db
). It could explain validation errors on the browser JavaScript console, roll back the offending changes, integrate with re-frame-10x, ...kee-frame comes with such an interceptor, but it's focus is on other unrelated, new concepts (controllers).
Something similar was requested in #457, but the main focus of that ticket lies elsewhere.
The text was updated successfully, but these errors were encountered: