Schema change (disputes)-- add payment intent dimension#190
Open
Ella6882 wants to merge 2 commits intosinger-io:masterfrom
Open
Schema change (disputes)-- add payment intent dimension#190Ella6882 wants to merge 2 commits intosinger-io:masterfrom
Ella6882 wants to merge 2 commits intosinger-io:masterfrom
Conversation
Latest changes from master branch in original repo
Author
|
@rdeshmukh15 @bhtowles I am looking for some eyes to bring in some fields that are missing in existing schemas for tap-stripe. Any help would be greatly appreciated |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 seen here (https://stripe.com/docs/api/disputes/object), payment_intent is missing from disputes schema.
Adding this field.
Manual QA steps
Risks
Rollback steps