Closed sagikazarmark closed 10 years ago
I don't see why you would ever need this. What is the use case? I have never come across a scenario where I have wanted to check if a field does not exist in my data.
I also have to admit that it is a questionable solution.
Think about a CRUD model where you want to have some fields read-only.
I would just ignore them when setting or unset them first. I don't think this rule should be included in the core library, especially seeing you can easily add your own on a per-project basis.
Inverse of Required rule