ephetic/functional

ES6 Functional Helpers

functional's Issues

Use CI

Add support for object matching

'Or' semantics

Custom predicate would already work, but it might be nice to specify multiple shapes/basic-predicates like m([m.OR(Number, String), fn])

close

12

Contructors as condition get called and usually truthy

import { matcher as m } from '@ephetic/functional'

const secondIsNumber = m(
  [ [m, Number], (a,b) => console.log(`${b} is a Number`)],
  [ [m, Array],  (a,b) => console.log(`${b} is an Array`)],
  [ m,           (a,b) => console.log(`${b} is not a Number or Array`)]
)

secondIsNumber('asdf', 2)   // 2 is a Number
secondIsNumber(2, {})       // [object Object] is an Array
secondIsNumber(2, 'asdf')   // asdf is an Array

Limit arg length

For Array conditions (i.e. argument checking), look into only passing as many arguments to fn as the length of the argument pattern, i.e. fn.apply(null, args.slice(0, cond.length).

This might be useful for when m functions are passed as callbacks to things that pass extra arguments. Wait, no; it's patterns will have to match those arguments. How about when the m function is given a callback as fn that expects an unknownish number of args. Yeah, maybe.

If nothing else, it would make it more predictable.

Create array checking example

Can't match zero arguments

[] is matched against anything rather than only matching a zero-argument call

Allow predicate matching in arguments

e.g. m([[Integer, Integer], () => console.log('int')])(1,2)

Check [head, ...rest] and object wrapping semantics

Not sure they even work. Once verified, improve the README.md notes on Arrays.

Array and rest matching

Since arrays are used to represent a parameter pattern, a literal array must be wrapped in an object {foo: [11,22,33]}. However, it would be nice to make sure the [head, ...rest] semantics work.

Use quick-check

Refactor as ES5 or as ES6 module with dist

Refactor prototype