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.
Description of change
As discussed #92
This allows users to opt-out of the metafield.value "parse json_string" behavior. I needed this because my desired target (singer-target-postgres) did not support a single field being int/string/object.
The Shopify API returns a string field, this feature lets the user keep it a string.
QA steps
I've been running this locally against our live Shopify store. I've observed it correctly working (keeping metafield.value as a string type when metafield.value_type is json_string). I've observed this allowing this shopify value to end up in my postgres db via singer-target-postgres, solving my problem.
Risks
This adds a small amount of surface area to the code, but this doesn't appear to interact with anything else in the program.
Rollback steps