You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not a fan of mixing schema definitions with data transformation to be honest. I do want to provide tools for converting data though. We can have Drops.Transformer or something that can perform key renaming and other types of common transformations. We could still provide a streamlined API for this, it's just that I don't want it to be mixed inside of schema DSL.
It would be nice to be able to map input keys to different output keys, similar to the
key:
option of Parameter.This would allow to easily convert between different field names across boundaries at data ingestion point.
For example, something like this (I'm using two different imaginary options in the example)
Which would allow me to conform the input map (e.g. from
Jason.decode
)Into the output map:
The text was updated successfully, but these errors were encountered: