This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
Data would all be lowercase + fix setup + update data pipeline #86
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.
Tower names, ability names, descriptions, are now all stored in lowercase in the database.
The graphql query arguments will be converted to lower case first before we use them to query
the database. Updated all tests accordingly.
Solves: Make all ability names, tower names, ability descriptions all lower case before storing in json or in the table #79
Fix data saving pipeline
seed/populate.js
only allows forinserts
and notupdates
. In the future, I might change this, but since the data isn't that much anyway, the current implementation is that the user is dropped and recreated and all the data are populated all over againImprove data saving pipeline #43