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

🚚 [MIGRATION] Use pkg/io instead of poly-go/io #271

Merged

Conversation

manoranjith
Copy link
Contributor

  • Because, the encoder/decoder implementations are specific to go-perun.

  • And the package will be modified in upcoming changes.

Signed-off-by: Manoranjith ponraj.manoranjitha@in.bosch.com

Copy link
Contributor

@matthiasgeihs matthiasgeihs left a comment

Choose a reason for hiding this comment

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

What is tags? Probably should be removed.

If pkg/io is Perun specific, would it make sense to place it into a more specific location? e.g., together with the other encoding logic?

- Because, the encoder/decoder implementations are specific to go-perun.

- And the package will be modified in upcoming changes.

Signed-off-by: Manoranjith <ponraj.manoranjitha@in.bosch.com>
@manoranjith
Copy link
Contributor Author

Removed the tags `file.

Regarding placement of the file, I have moved it back into its original location. Moving this file to a more appropriate location, can be done in a separate PR, because we anyways have to re-organize this package and its contents, as a part of #233.

Also, another open PR (#258) expects this to be in pkg/io. If we move this now, then #258 should also be reworked.

@matthiasgeihs matthiasgeihs merged commit 24bd110 into hyperledger-labs:dev Nov 30, 2021
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.

None yet

2 participants