* Modify to fix arguments with object contains newline in arrow function(nested)
* Update CHANGELOG.unreleased.md
* Update tests
* Modify to refactor
* Modify to refactor
* Add pr number and link
* Update CHANGELOG.unreleased.md
* Modify to remove unnecessary null checking
* Fix for ArrayPattern
* Fix for RestElement
* Fix for AssignmentPattern
* Update tests
* Fix for nested array and object
* Update tests
* Fix for nested array pattern
* Update tests
* Modify to discard unnecessary node type check
* Fix for rest element
* Fix for array in rest
* Fix for array in assignment pattern
* Update tests
* Fix for CallExpression with Assignment
* Fix for ArrowFunction with AssignmentPattern
* Update tests
* Modify to support generally pattern
* Update tests
* Modify to use path.each instead of path.map
* Fix for multi arguments
* Fix typo, Argments => Arguments
We don't always want to automatically forward this option but we can always forward it to `n.body`. If it's an arrow function, it's doing the intended behavior, otherwise, it's not going to ignore it and not forward it. What we don't want is for arrow -> blockStatement -> arrow to get it, but we're good.
Fixes#1652
In practice, trying to allow calls to be inlined is causing a lot of code to look very weird and unstable as seen by the four issues this is fixing. It also requires us to add a conditional group and do hackery around it.
Fixes#959Fixes#760Fixes#615Fixes#625
Sosuke Suzuki