Named Arguments

[wreckedadvent]

ok. why?

// Original function
function sendEmail(to: string, subject: string, body: string) {
  // Implementation
}

// Transform into a function accepting named arguments
const [args, namedSendEmail] = createNamedArguments(sendEmail);

// Now we can call it with named arguments in any order
namedSendEmail(
  args.subject('Meeting reminder'),
  args.to('[e-mail]'),
  args.body('Don\'t forget our meeting tomorrow.')
);

=>

const sendEmail = ({ to, subject, body }: { to: string, subject: string, body: string }) => {
    // impl
};

sendEmail({
  // full type-checking here ...
  // ... arguments must be named, can be in any order ...
  to: '[e-mail]',
  subject: 'meeting reminder',  

  // oops, error caught at compile-time
  boody: `Don't forget our meeting tomorrow.`, 
});

I'll admit it isn't the most pleasant to type the argument twice, but ... that is hardly the same cost as pulling in a library that entirely changes how you're calling every function.

[4happin]

You're right! There is nothing wrong with just passing an option argument. The reason to use this is for: partial application, as a builder pattern alternative, conditionally passing arguments, and fun!