refactor: package cleanup - #4808
Merged
Merged
Conversation
julienrbrt
marked this pull request as ready for review
October 2, 2025 19:38
Contributor
|
The |
Member
Author
Correct but the app wasn't maintained and it was only used on that package. If we keep maintaining network, we can just bring the relevant function then. This decrease maintaining surface in the cli. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proceeding to do some package clean-up.
Talked to some users and they find the amount of package to be used not clear.
They'd rather see package they could use directly for they chain / tooling, such as the cosmosclient, cosmostxcollector, etc...
I moved a bit of things in #4805, but continuing here for clarity.