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

feat: Event Stream refactor #173

Merged
merged 7 commits into from
Oct 28, 2024
Merged

feat: Event Stream refactor #173

merged 7 commits into from
Oct 28, 2024

Conversation

cynicaljoy
Copy link
Contributor

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

    • Bug fix (non-breaking change that fixes an issue)
    • New feature (non-breaking change that adds functionality)
    • Breaking change (backwards-incompatible fix or feature)

Checklist:

    • My code follows the code style of this project.
    • My change requires a change to Fauna documentation.
    • My change requires a change to the README, and I have updated it accordingly.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

client.go Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@pnwpedro pnwpedro left a 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

client_example_test.go Show resolved Hide resolved
client_example_test.go Show resolved Hide resolved
@cynicaljoy
Copy link
Contributor Author

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?

@pnwpedro
Copy link
Collaborator

pnwpedro commented Oct 25, 2024

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?

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.

Copy link
Contributor

@jrodewig jrodewig left a 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.

Copy link
Contributor

@erickpintor erickpintor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@cynicaljoy cynicaljoy merged commit 42c684b into main Oct 28, 2024
5 checks passed
@cynicaljoy cynicaljoy deleted the refactor-stream branch October 28, 2024 18:55
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

Successfully merging this pull request may close these issues.

4 participants