Add a test for combine and the use of two files with the same name in different directories#183
Open
parmentf wants to merge 1 commit into
Open
Add a test for combine and the use of two files with the same name in different directories#183parmentf wants to merge 1 commit into
parmentf wants to merge 1 commit into
Conversation
When two files with the same names, but not in the same directory are called, they should each have their own behaviour, not the one of the first encountered file.
Collaborator
Author
|
I must have missed something, as I can't understand why the output I got is: [ { "a": { "id": { "id": 1, "value": "a"}, "value": { "id": 1, "value": "a" } } } ]instead of the (bugged) expected: [{ "a": "a" }]Whereas, if it worked well: [{ "a": "b" }]@touv , an idea ? Precision: when I don't apply the second [{ "a": { "id": 1, "value": "a" } }] |
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
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.
When two files with the same names, but not in the same directory are
called, they should each have their own behaviour, not the one of the
first encountered file.
See this issue.