Created a database for buglog (user story 2) #32
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
Pull Request Test Coverage Report for Build 11014400300Details
💛 - Coveralls |
aattiyah
added
backend
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.
Created a database for buglog to be able to store the data, it will take the data that the client has reported on the form and store it in the bug-log page located in the admin side bar section.
With regard to creating the database, in public/openapi/read/admin/dashboard I created a bug-logs.yaml page then modified the read.yaml to make sure it has included bugle. In public/openapi/components/schemas I created a file called BugLogObject.yaml which is a schema to define the structure of bug log objects returned by the API.
This tackles part of issue #8