req / user access in condition callback

[ssyberg]

We have many uses cases for field level access control were using access is a bit clunky and it would be much nicer/easier to just hide fields that users shouldn't touch. Currently condition callbacks only accept data and siblingData

[DanRibbens]

I looked at adding user to the arguments for condition functions and I see that the type on this function isn't ideal for expanding it. Since it is called with (data, siblingData) I have to add user as the 3rd argument on the function. This works, but I am fairly confident there will be a breaking change as we're going to want move to an argument object to make this future proof.

I'm moving ahead with (data, siblingData, { user }) for now.

[DanRibbens]

#2543

[ssyberg]

Yea I was a bit surprised by the callback args in condition it does seem to break the pattern across the other hooks/callbacks but this solution seems reasonable to me!

[DanRibbens]

We can break from this in 2.0.