Skip to content
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.

Consider factoring of ModelMetadata #1477

Closed
rynowak opened this issue Oct 29, 2014 · 2 comments
Closed

Consider factoring of ModelMetadata #1477

rynowak opened this issue Oct 29, 2014 · 2 comments

Comments

@rynowak
Copy link
Member

rynowak commented Oct 29, 2014

ModelMetadata contains data today used for the following purposes:

  • Structure (properties/types)
  • Display (data-annotations)
  • Validation (data-annotations, requiredattribute)
  • Model Binding (bindattribute, frombodyattribute)

To extend the set of provided data or customize discovery, users must author an IModelMetadataProvider, which is very complex.

We should think about the factoring of what data needs to be part of ModelMetadata and what can be moved to a higher level. This could make authoring an IModelMetadataProvider easier, increase cacheability, etc.

@dougbu
Copy link
Member

dougbu commented Oct 29, 2014

see also #476, #1034, and #1407. there's also a number of low-level bugs about pieces missing from the current ModelMetadata hierarchy e.g. #1000 and #1021.

@rynowak
Copy link
Member Author

rynowak commented Mar 13, 2015

90cef3b

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants