feat: add channel invitation data model#786
Open
Pranav-d33 wants to merge 3 commits into
Open
Conversation
Pranav-d33
force-pushed
the
feat/channel-invitation-workflow-part-2
branch
from
422eb3a to
fcc3af0
Compare
Author
|
Ready for review. Let me know if any changes are needed for merge. |
Signed-off-by: Pranav dhiran <dhiranpranav72@gmail.com>
Pranav-d33
force-pushed
the
feat/channel-invitation-workflow-part-2
branch
from
fcc3af0 to
3457e11
Compare
Signed-off-by: Pranav dhiran <dhiranpranav72@gmail.com>
Pranav-d33
force-pushed
the
feat/channel-invitation-workflow-part-2
branch
from
3457e11 to
5a4d05e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 2 of the channel invitation workflow.
Adds API engine data foundations for the multi-party channel invitation flow:
This PR does not add endpoints or Fabric agent behavior yet. Those will follow in separate PRs.
Related: #772