Of course, and I don’t want to do that.
The course of action I want to prevent is the following:
- The developer make a specific tree view editable
- The user can make optional per your proposition, thus he removes a required field
- The view is broken
But a silly developer could make this:
- Make a view editable
- Make each field on the view optionable
- The user does something stupid
- The view is broken
I want to prevent the first case, not the second.