Often times we have to deal with data in complex formats involving heavy nesting. This becomes very error prone when code doesn't properly validate the full property path (in particular in dynamic languages such as nodejs).

function myLogic (foreignObject) {
  const myNewObject = {
    blub: foreignObject.blubWrapper.flub.blub,
    flub: foreignObject.blubWrapper.flub.flub,
    foo: foreignObject.foo,
    bar: foreignObject.foo.bar,
  }
  // something would happen here, but
  // foreignObject had a missing
  // node in the property path!
}
    

Rolling Pin

With Rolling Pin, you can easily treat these input/output object maps as data, instead of bungling it with your code.

First, upload your own JSON. Second, personalize the mapping of that data. Third, copy the "Currently mapped aliases" and use one of the available libs to seamlessly integrate this into your own codebase!

Before:
{
}
      
After:
{
}
      

Currently mapped aliases: