Introduce project dashboard skeleton #54
Draft
Conversation
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
In particular, this encapsulates data loading, defines an issue + issue repository domain layer, encapsulates GraphQL querying, and slightly improves async function management via promises so that we explicitly handle success/failure. Also, fill in TODOs for future functionality that we need to add.
Spec out more of the domain objects needed in the domain layer, add some documentation for issues to establish a document style & level of detail, and add a high-level diagram of the organizational break-down.
|
Note that TODOs still need to either be resolved or converted to issues. |
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.
This PR aims to introduce the high-level data layering of the project dashboard & specific implementations for the domain layer including hook-ins into GraphQL using an abstracted data loader layer (which will make caching easier later on).