Sounds like we're on the same page pretty much. If we merge #62 then I think we can let users register their models with the fluent API, and then there is no need to expose IModelManager to them. We might need some other interface to facilitate registration. Something like:

public interface IResourceTypeRegistrationProvider
{
    Type[] RegisterTypes();
}

public class MyResourceTypeRegistrationProvider : IResourceTypeRegistrationProvider
{
    ...
}

new JsonApiConfiguration()
    .RegisterTypesUsing(new MyResourceTypeRegistrationProvider());

Regarding the MetadataManager, I think we can avoid needing to steal the DependencyResolver by using a custom model binder and then passing an IMetadataManager instance to action methods. So the PUT method signature would change to:

Task<IList<T>> Put(string id, IList<T> putObjs, IMetadataManager metadata);

I'm not entirely sure that this is possible, but I'll look into it when I get a chance. If it works, then we can finally get rid of the singleton MetadataManager and make it a constructor param for JsonApiFormatter.

Uh oh!

polymorphism #73

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions