Skip to content
This repository was archived by the owner on Jan 6, 2025. It is now read-only.

expose message type id#52

Closed
johncantrell97 wants to merge 1 commit into
lightningdevkit:mainfrom
johncantrell97:message-type-id
Closed

expose message type id#52
johncantrell97 wants to merge 1 commit into
lightningdevkit:mainfrom
johncantrell97:message-type-id

Conversation

@johncantrell97
Copy link
Copy Markdown
Contributor

this became hidden in the refactor. it is needed when a user is writing their custom message handler.

@johncantrell97
Copy link
Copy Markdown
Contributor Author

hm I guess maybe user might not need it. could just give all custom messages to the handler and it will return Ok(None) if it doesn't know about the message type?

@tnull
Copy link
Copy Markdown
Collaborator

tnull commented Nov 29, 2023

this became hidden in the refactor. it is needed when a user is writing their custom message handler.

Yeah, this was kind of intentional. We'll revisit where we should expose which types when tackling #36. We may want to expose said id then under lsps0.

@tnull
Copy link
Copy Markdown
Collaborator

tnull commented Dec 6, 2023

Now superseded by #58.

@tnull tnull closed this Dec 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants