-
Notifications
You must be signed in to change notification settings - Fork 186
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
add abstraction to manage shape request-response behaviour #2273
Conversation
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
9917d15
to
13bb6c4
Compare
and configure the application with it
it's probabaly just that the shape wasn't created
make sure the sync has at least initialised before dropping the table
ea6edeb
to
c0e4d05
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This a great change. I think this encapsulation is worth it and makes parts of the flow much cleaner. I think some nested structure updates are a bit hard to follow at times, but that's OK. I have some nitpicks, with only blocking request being the one about exposing stacktraces
Co-authored-by: Ilia Borovitinov <[email protected]>
add some convenience functions to clean up the api just return a response from do_serve_shape_log normalise error messages
Used by #2297