Pass the field/key when errorMessage is a function

[Emilios1995]

It is very common to include the name of the field in the error message. I thought it convenient to include pass it when errorMessage is a function.

Here's how I'm using this feature (from my fork):

const isType = R.curry((type, field) => R.type(field) === type);
const typeMessage = (type, field) => `${field} has to be a ${type}`;
const typeRule = (type) => [
  isType(type),
  (val, field) => typeMessage(type, field)
];

const validationRules = {
  name: [typeRule("String")]
}

[busypeoples]

I like the approach, very nice example of how to create a [pred, errorMsg] tuple.

const typeRule = (type) => [
  isType(type),
  (val, field) => typeMessage(type, field)
];

Just so I fully understand, this:

const isType = R.curry((type, field) => R.type(field) === type);

should be:

const isType = R.curry((type, val) => R.type(val) === type);

right?

[Emilios1995]

Exactly! Sorry, my bad.

[busypeoples]

Yes, I think this is very cool!

[busypeoples]

We should add this to the 0.6 release. Will probably merge this tomorrow. I also like the example

const validationRules = {
  name: [typeRule("String")]
}

shows how nicely one can create rules.

[busypeoples]

@Emilios1995 Great work!

[Emilios1995]

Thanks, I'm glad you liked it!

[Emilios1995]

We should also document this in the API docs. I'll probably make a commit for that later.

[busypeoples]

We should als add a test, but I can write that one tomorrow, if you have no time for that.

[Emilios1995]

@busypeoples I'll try to do both things tonight. I'll ping you tomorrow if I have any trouble.

[Emilios1995]

Done! But I'm not sure if I left that test too complex or the docs too verbose. What do you think?

P.S. I would also love to see something like my typeRule function somewhere in the readme, but I'll leave that to your consideration.

[busypeoples]

@Emilios1995 Thank you very much! I'll look into it in more detail in a couple of hours. But looks good after quickly going through the commits. I will merge later on today.

[busypeoples]

Regarding the typeRule, definitely. That example you have is more than elegant, and displays nicely how one can compose rules to bigger rules etc.