-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: Event Stream refactor #173
Conversation
e4eea78
to
a8f11e6
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 lgtm, but don't we have to increment to v3 everywhere before we make these changes? https://github.com/search?q=repo:fauna/fauna-go%20v2&type=code
my plan was to merge this to main and then version bump in a separate PR. do you think we should version bump within this one? |
b6c9ffb
to
93148b4
Compare
yeah, i was thinking we'd move to v3 before. we can always cherry pick something to v2 and adjust the pipeline to deploy it if needed. |
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.
LGTM. I pushed some updates to the README as a few things were wonky. Sorry for the noise there.
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.
LGTM
c5ff934
to
119944b
Compare
ENG-6824
Description
Rename the Event Stream resources
Motivation and context
Consistent naming between the Features and the drivers
How was the change tested?
Unit/Integration tests
Screenshots (if appropriate):
Change types
Checklist:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.