added resolvers and modified typeDfs #61
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
This was
linked to
issues
Jan 21, 2021
Closed
Closed
Closed
Closed
LUXIANZE
requested changes
Jan 21, 2021
LUXIANZE
requested changes
Jan 22, 2021
LUXIANZE
reviewed
Jan 23, 2021
LUXIANZE
reviewed
Jan 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For audioContent which is suppose to have Buffer type (based on model), I changed it to be string type in typeDfs. Need to change it to suitable type.
Similarily, upload part of the audioStorage is coded by following this.
However, I think we need to do something like this link but I not sure ah.
NOTE: all delete part now returns a string, following how Yaw did.