This repository has been archived by the owner on Nov 5, 2019. It is now read-only.
Task Pipeline frontend & Collections Support #37
Merged
Conversation
This file contains 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
|
I'm going to merge this, as a good chunk of the discussion happened over on task-mgmt task refactor PR |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR brings initial support on the frontend for both tasks & collections. This can only be merged after we merge the task-mgmt queue refactor.
The tasks implementation is extremely skeletal, only one type of task is supported: archiving a url to IPFS. The main job here is to demonstrate the task queue working from end-to-end.
Collections, on the other hand, are much more complete. I think we'll find them useful right off the bat.