Portal backend api#151
Merged
Merged
Conversation
This will be a replacement of the FlowController trait. We temporarily need two different implementations of dyn-compatible trait, but in order to make an async fn, we use a struct that forwards over a channel.
iinuwa
force-pushed
the
portal-backend-api
branch
from
be8f4a8 to
65cf12d
Compare
Member
Author
|
Little quick and dirty, but it works as a first draft. There are more changes to make this more like a normal portal API, so I will clean up in subsequent PRs. |
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
1 participant
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.
Add implementation of portal backend API.
This is a work-in-progress as the spec evolves
Depends on #148