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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cypress-test): include worldpay's request / response structure for test suite #6420
feat(cypress-test): include worldpay's request / response structure for test suite #6420
Changes from all commits
8a3eb67
48bdbf4
009a899
e32eeb7
389a699
fd9341a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we could do a deep merge of
commons.js
and<connector>.js
in a safer way that does not overrides the existing configs from<connector>.js
, this change would never be needed.as discussed, deep merge will for sure add overhead, but would reduce complexity is what i feel.
this should also work, but i do think this will have a very limited scope of use.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does have a very limited scope as of now, we can remove this once we introduce custom deep merge (merge everything except
Response
). But we can let it be for now, since it's out of scope of this PR