⚡ flow: Avoid multiple reinstanciations

[nlepage]

Issue : fix #137

[codecov-io]

Codecov Report

Merging #149 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #149   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          77     77           
  Lines         280    294   +14     
=====================================
+ Hits          280    294   +14

Impacted Files	Coverage Δ
packages/immutadot/src/core/apply.js	100% <100%> (ø)	⬆️
packages/immutadot/src/core/path.utils.js	100% <100%> (ø)	⬆️
packages/immutadot/src/flow/flow.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 79d0b59...e7d7933. Read the comment docs.

[nlepage]

For now "already applied paths" are theoric.
For paths containing slices this means that we don't really know if copies were made, which indexes of slices were copied, the entire structure might not have been copied...
That's why path containing slices are filtered from already applied paths...

@frinyvonnick What do you think we should do ?

• Merge this as it is (with docs, tests, and possibly refactoring) and try to improve in the next version
• Not merge this
• Refactor apply to have really applied paths

[frinyvonnick]

I would opt for the first proposal and we open an issue about a future refatoring 👍

[frinyvonnick]

👏

[nlepage]

See #153 for further improvements of apply