fix: convert "type" Enums to strings in v1 recipe for firebase upload duplication check #231
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.
Problem
What is the problem this work solves, including
Found a bug: a v1 recipe could be uploaded to firebase more than once
This issue arises because, during the version migration process, the "type" attribute of an object is converted into an Enum, whereas it is stored as a string in firebase database. So our duplication checking logic always find a difference in data types.
difference:
Solution
What I/we did to solve this problem
I added a value check for enum in the existing method
prep_data_for_db
withinDBRecipeHandler
Type of change
Please delete options that are not relevant.
Steps to Verify:
DBRecipeHandler.py
, comment out thereturn
inDBUploader > upload_recipe()
to let deeper system checks into objects and compositionsupload -r examples/recipes/v1/one_sphere.json
to upload the recipe to your dev database