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.
Fixed output issue with zigzagLevelOrder function
As the expected result, as mentioned above in the file was:
[
[3],
[20,9],
[15,7]
]
The function was returning the result as:
[
[3],
[9,20],
[7,15]
]
I was struggling myself to know the input for the zigzagLevelOrder function.
Found it at last. And wanted to contribute it. Thought it would be helpful to others.
So I added a input variable binaryTree with the value, which is an input to zigzagLevelOrder function,
And also consoled the result with an index.html file, so that people can just clone the repo and see the result in browser
console quickly and play around.
Update the zigzagLevelOrder function to arrow function and change var to const declaration.