Feature: Implements MapFields()

[Paulholio]

This is an attempt at eventually implementing the feature request from:

Issue 285: Updating All Fields

There is more work that needs to be done, but I think if we can spec out what types of operations we would want future users to be able to do across all fields, this can become very useful, especially on the validation and possibly security front. Let me know your opinions on this, please.

[hartym]

Hello,

Thanks for your contribution. A few things:

• Let's call this MapFields, to be named like python's map() builtin (but refers to "fields", as we could have a Map that does this logic on a whole row)
• Let's use the python callable to apply instead of a string : pass str.upper as parameter to the transformation, so it allows to use any callable the same way. The usage would then be MapFields(str.upper), or MapFields(lambda val: ...), etc. Much more flexible and less error prone as we'll need less code.
• Please add an unit test (even if not very complete) to check that this continue to work over time, and to check that edge cases work as expected (what if we get an empty row? what if we pass mixed type rows?)
• In the future, but let's not implement it in the first version, we could improve it by allowing the user to pass a list of fields to apply this to, or a callable to chose which fields to apply this to.

Thank you, this is a nice one !

[Paulholio]

I have this renamed to MapFields and will have users pass in a function. Still need to write a unit test.

[hartym]

This pull request introduces 1 alert when merging 166e846cc740e2a0e7008297095796c9269170be into ca464ef6f754c2e5bb7aa7632bb4190e6b39a037 - view on LGTM.com

new alerts:

• 1 for Except block handles 'BaseException'

---

Comment posted by LGTM.com