[FEATURE][ADD] Add forOwn and forOwnRight

[Chalarangelo]

Description

Two methods for objects from lodash.

Lodash[ADD] #100 -> https://lodash.com/docs/4.17.4#forOwn
Lodash[ADD] #100 -> https://lodash.com/docs/4.17.4#forOwnRight

What does your PR belong to?

• Website
• Snippets
• General / Things regarding the repository (like CI Integration)
• Tests

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Enhancement (non-breaking improvement of a snippet)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Lodash Backlog

• I added the prefix [UPDATE: method.md] or [ADD: method.md]
• I have referenced the method to the lodash backlog.

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have checked that the changes are working properly
• I have checked that there isn't any PR doing the same
• I have read the CONTRIBUTING document.

[skatcat31]

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/entries if only this were ES6...

[skatcat31]

Should we call this forOwn or should we make it an object copier that is more akin to a mapObj? Or should we do a mapObj function alongside/at all?

[Chalarangelo]

I'm thinking a mapObj function alongside this could be worthwhile as a matter of fact. While we're at it, maybe we should ditch the forIn and forInRight ones, as they are too much trouble and I do not see any reason to really add those very specific functions to begin with.

[skatcat31]

Although to be fair map object is a slightly more advanced and somewhat confusing snippet

[skatcat31]

Significantly different and simpler than how you would create a mapObj function

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for any follow-up tasks.