Skip to content

use absolute exclude path in build/webpack.test.config.js and fix error when recursively traverse an object #2680

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

Closed
wants to merge 5 commits into from

Conversation

flytreeleft
Copy link

@flytreeleft flytreeleft commented Apr 16, 2016

  • use absolute path to make sure running tests is OK even if it is in node_modules of other project
  • fix 'Maximum call stack size exceeded' when recursively traverse an object

@flytreeleft flytreeleft changed the title use absolute exclude path in build/webpack.test.config.js use absolute exclude path in build/webpack.test.config.js and fix 'Maximum call stack size exceeded' when recursively traverse an object Apr 16, 2016
@flytreeleft flytreeleft changed the title use absolute exclude path in build/webpack.test.config.js and fix 'Maximum call stack size exceeded' when recursively traverse an object use absolute exclude path in build/webpack.test.config.js and fix error when recursively traverse an object Apr 16, 2016
var i, keys

!walkedObjs && (walkedObjs = {})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious about this notation. How is it different from walkedObjs = walkedObjs || {} ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uh, it's just personal habits, there is no difference between them, do not be feeling trouble with it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't complaining, just curious 😄

@yyx990803
Copy link
Member

Please do not mix multiple fixes in the same PR, since this makes it harder to review and merge. Submit separate PRs please.

@flytreeleft
Copy link
Author

Splitting to #2686 and #2685

@flytreeleft flytreeleft deleted the cherry-branch branch April 17, 2016 05:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants