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

voyager libraries improvements #2991

Open
benluelo opened this issue Sep 20, 2024 · 0 comments
Open

voyager libraries improvements #2991

benluelo opened this issue Sep 20, 2024 · 0 comments
Assignees
Labels
A-voyager Area: Our voyager relayer C-enhancement Category: An issue proposing an enhancement or a PR with one. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate.

Comments

@benluelo
Copy link
Contributor

benluelo commented Sep 20, 2024

voyager-message is currently very monolothic. it should be split into a few separate parts:

  • voyager-core: various types used throughout the voyager stack (i.e ChainId, IbcInterface, ClientInfo, etc). this will be depended on by all other libraries.

  • voyager-sdk: library used by plugin and module authors. potentially split this up further to voayger-module-sdk and voyager-plugin-sdk, depending on the design we land on for plugins and modules (see split voyager plugins and modules #2996). this will mostly be re-exports as well as some helper types.

  • voyager-message: actual voyager message types (i.e. Data, Call, Callback) and all the interfaces and implementations required for that directly.

  • voyager-rpc: contains the definition of the main VoyagerRpc trait.

  • another library that contains the plugin and module child process spawning and connectivity logic (voyager-supervisor? voyager-executor?)

@benluelo benluelo added C-enhancement Category: An issue proposing an enhancement or a PR with one. E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate. A-voyager Area: Our voyager relayer labels Sep 20, 2024
@benluelo benluelo self-assigned this Sep 20, 2024
@benluelo benluelo added the C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. label Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-voyager Area: Our voyager relayer C-enhancement Category: An issue proposing an enhancement or a PR with one. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate.
Projects
None yet
Development

No branches or pull requests

1 participant