Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AWS Amplify: Datastore] Create a new GraphQL schema to match existing database schema structure #54

Closed
DBarnes2 opened this issue Jul 15, 2021 · 0 comments · Fixed by #130
Assignees
Labels
task Development Tasks
Projects

Comments

@DBarnes2
Copy link
Collaborator

Storypoints: 2

This might be as simple as copy and pasting the existing schema definitions and adding a couple tags.

This should exist in the src/db folder.

Should only give users read access, as write access operations should still be done through APIs for now.

Context: https://github.com/gp-seattle/rms-app/wiki/AWS-Amplify-Project:-Datastore

@DBarnes2 DBarnes2 created this issue from a note in Backend (Sprint) Jul 15, 2021
@yauj yauj moved this from Sprint to In Progress in Backend Jul 15, 2021
@yauj yauj moved this from In Progress to Sprint in Backend Jul 15, 2021
@yauj yauj added this to the AWS Amplify Project: Datastore milestone Jul 15, 2021
@yauj yauj added the task Development Tasks label Jul 19, 2021
@johnnyhchen johnnyhchen moved this from Sprint to In Progress in Backend Jul 19, 2021
johnnyhchen added a commit that referenced this issue Jul 20, 2021
johnnyhchen added a commit that referenced this issue Jul 20, 2021
johnnyhchen added a commit that referenced this issue Jul 26, 2021
yauj pushed a commit that referenced this issue Jul 26, 2021
johnnyhchen added a commit that referenced this issue Aug 2, 2021
johnnyhchen added a commit that referenced this issue Aug 2, 2021
johnnyhchen added a commit that referenced this issue Aug 2, 2021
johnnyhchen added a commit that referenced this issue Aug 2, 2021
johnnyhchen added a commit that referenced this issue Aug 3, 2021
johnnyhchen added a commit that referenced this issue Aug 3, 2021
johnnyhchen added a commit that referenced this issue Aug 4, 2021
johnnyhchen added a commit that referenced this issue Aug 4, 2021
johnnyhchen added a commit that referenced this issue Aug 4, 2021
johnnyhchen added a commit that referenced this issue Aug 4, 2021
johnnyhchen added a commit that referenced this issue Aug 4, 2021
johnnyhchen added a commit that referenced this issue Aug 4, 2021
johnnyhchen added a commit that referenced this issue Aug 4, 2021
johnnyhchen added a commit that referenced this issue Aug 5, 2021
johnnyhchen added a commit that referenced this issue Aug 5, 2021
@yauj yauj moved this from In Progress to In Review in Backend Aug 5, 2021
Backend automation moved this from In Review to QA Aug 5, 2021
johnnyhchen added a commit that referenced this issue Aug 5, 2021
Created GraphQL Schema
Russell500 pushed a commit that referenced this issue Aug 5, 2021
NavigSB pushed a commit that referenced this issue Aug 9, 2021
GH-131: Fix ItemTable key

GH-133: Update key for items table

GH-127: Added Action Dialog

* GH-127: Added Action Dialog

* GH-127: Dim background attempt

* GH-127: Added Action Dialog

* GH-127: Added Action Dialog

* GH-127: Added Action Dialog

* GH-127: Added Action Dialog

* GH-127: Added Action Dialog

* GH-127: Added Action Dialog

* GH-127: Fixing errors

* GH-127: Revisions

GH-115: Create method in AddItem to auto-generate the ID (#142)

GH-121: Function Integration Tests (#141)

* GH-121: Functions Integration Tests

GH-143: Change History item id to be called itemId

* GH-143: Change History item id to be called itemId

* Update seeds to let tests pass

GH-20: Move ts-code outside of amplify/backend directory

- Because that directory gets overidden on git pull
- Also Integration test after amplify push

GH-116: Auto-Supply ID during AddItem

Created functional tab navigation system
@yauj yauj moved this from QA to Done in Backend Aug 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task Development Tasks
Projects
Development

Successfully merging a pull request may close this issue.

3 participants