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

Support Decoding Message Data from MessageOut Receipt #3179

Open
Torres-ssf opened this issue Sep 17, 2024 · 3 comments
Open

Support Decoding Message Data from MessageOut Receipt #3179

Torres-ssf opened this issue Sep 17, 2024 · 3 comments
Labels
feat Issue is a feature

Comments

@Torres-ssf
Copy link
Contributor

We should consider adding a feature to the SDK to decode the Message data property, as this functionality could be beneficial for certain users.

It may also be possible to decode this on the fly when parsing the MessageOut receipt.

More context on the following discussion.

@Torres-ssf Torres-ssf added the feat Issue is a feature label Sep 17, 2024
@maschad maschad assigned maschad and unassigned maschad Sep 18, 2024
@maschad
Copy link
Member

maschad commented Sep 20, 2024

Unassigning myself from this after a conversation with @nedsalk this will be apart of the broader ABI refactor in #3085

Copy link
Contributor

  • Users need to be able to define their own coders for this to work completely.

  • Coders for functions/configurables, etc. will use a Sway spec version of encoding. However, messages may require custom coders to be passed in which don't match the spec, because their encoding is left for the user to define. (relates to Encoding for messages, SMO sway#5514)

Copy link
Contributor

We will allow users to pass through custom coders to be pass in with TS-599

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat Issue is a feature
Projects
None yet
Development

No branches or pull requests

3 participants