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

Remove defunct protos #202

Merged
merged 4 commits into from
Sep 4, 2024
Merged

Remove defunct protos #202

merged 4 commits into from
Sep 4, 2024

Conversation

richardhuaaa
Copy link
Contributor

@richardhuaaa richardhuaaa commented Sep 3, 2024

There is a bunch of defunct code on both client and server I want to clean up - this should be helpful for new hires, backwards-compatibility for the replication project, debugging, and auditability. Starting with the protos first

@richardhuaaa richardhuaaa requested a review from a team as a code owner September 3, 2024 23:08
@richardhuaaa richardhuaaa changed the title refactor: remove defunct protos Remove defunct protos Sep 3, 2024
Copy link
Collaborator

@neekolas neekolas left a comment

Choose a reason for hiding this comment

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

Thanks for tackling. Think this checks off a few boxes in Phase 2 of this issue

@richardhuaaa
Copy link
Contributor Author

Ah, I totally missed that you were on it! Sorry for pre-empting you

@richardhuaaa richardhuaaa merged commit 5e53523 into main Sep 4, 2024
4 checks passed
@richardhuaaa richardhuaaa deleted the rich/remove-unused branch September 4, 2024 01:44
Copy link

github-actions bot commented Sep 4, 2024

🎉 This PR is included in version 3.67.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

richardhuaaa added a commit to xmtp/libxmtp that referenced this pull request Sep 4, 2024
This is a follow-on to xmtp/proto#202, to remove defunct code that may cause confusion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants