`BindNever`, `JsonIgnore`, and `BindRequired`

When using the entity model as the resource model, it is useful to be able to use the BindNever, JsonIgnore, and BindRequired attributes. This way you can easily specify which properties should be hidden from the client and how. As far as I know, you can’t do this with the current implementation (these attributes simply don’t work).

[jaredcnance]

Ah, I see. So, there are 2 requirements currently not met:

1. Allow read-only attributes which cannot be set on POST
2. Improve portability of pre-existing models by supporting Newtonsoft attributes and ASP.Net model binding attributes

By implementing 2 we also implement 1. I think this will take a little bit of research to do properly. When I have time I’ll spec out the requirements for the implementation in this issue.

[bart-degreed]

As mentioned earlier, we cannot propagate all custom attributes on resource properties. Our recent switch to System.Text.Json does not change that.

However:

• We do provide AttrCapabilities, which enables devs to specify setting a value on POST and/or PATCH is not allowed.
• We have working ASP.NET model state validation, so you can put [Required] on properties. This works correctly when combined with partial patch. Note this is turned off by default.

I believe these address the requested functionality, so I’m closing this. It does not enable reusing existing models with Newtonsoft or System.Text.Json annotations, but as explained earlier I don’t think we can solve that.