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

Restructure the ibc crate to mirror ibc-go's structure #1436

Closed
5 tasks
seanchen1991 opened this issue Oct 7, 2021 · 0 comments
Closed
5 tasks

Restructure the ibc crate to mirror ibc-go's structure #1436

seanchen1991 opened this issue Oct 7, 2021 · 0 comments
Labels
I: dependencies Internal: related to dependencies O: code-hygiene Objective: cause to improve code hygiene
Milestone

Comments

@seanchen1991
Copy link
Contributor

Crate

The ibc crate

Summary

Clean up the structure of the ibc crate so that it mirrors the structure of ibc-go, more specifically splitting the contents between Core components (Clients, Connections, Channels, etc.), Applications (Fungible Token Transfers, Interchain Accounts, etc.), and Light Clients (Tendermint).

Problem Definition

This will help to consolidate repository structures across the main IBC implementations in the ecosystem. It will also more clearly delineate the logical structure of the ibc crate; the current crate structure doesn't really do a good job of this.

Proposal

Restructure the ibc crate to mirror ibc-go's structure.

Acceptance Criteria

The structure of the ibc crate mirrors ibc-go's structure.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@adizere adizere added O: code-hygiene Objective: cause to improve code hygiene I: dependencies Internal: related to dependencies labels Oct 14, 2021
@adizere adizere closed this as completed Nov 2, 2021
@adizere adizere modified the milestones: 12.2021, 10.2021 Nov 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: dependencies Internal: related to dependencies O: code-hygiene Objective: cause to improve code hygiene
Projects
None yet
Development

No branches or pull requests

2 participants