Allow paths to be excluded from transformation

[mojavelinux]

Allow certain paths to be excluded from transformation (excludePaths). This is necessary when certain subpaths of the structure hold pure data that are not part of the model. For example, one of the keys might hold key-value pair data, but that key-value pair data cannot be corrupted.

I'm imagining something like:

camelcaseKeys(raw, { deep: true, excludePaths: ['path.to.hash'] })

It would be the data inside this path, not the path itself, that would be excluded.

---

IssueHunt Summary

stroncium has been rewarded.

Backers (Total: $60.00)

• issuehunt ($60.00)

Submitted pull Requests

• #37 Add excludePaths and stopPaths options, fixes #23

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

---

IssueHunt has been backed by the following sponsors. Become a sponsor

[sindresorhus]

Sounds like a valid use-case. PR welcome.

[mojavelinux]

Great. That's what I needed to know.

[mojavelinux]

I was thinking about this question of whether the specified path itself should be excluded, or whether it just excludes its children. That got me thinking that perhaps the right name for the option is "stopPaths" instead of "excludePaths". (And, of course, this is related to the deep option). I'm open to suggestions, and that can be tuned once we're looking at some code.

[IssueHuntBot]

@IssueHunt has funded $60.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[issuehunt-oss]

@sindresorhus has rewarded $54.00 to @stroncium. See it on IssueHunt

• 💰 Total deposit: $60.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $6.00