-
-
Notifications
You must be signed in to change notification settings - Fork 158
Auto-Resource, Repository, and Service Discovery #241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Closed
This was referenced Jul 2, 2018
jaredcnance
added a commit
that referenced
this issue
Jul 5, 2018
fix(AttrAttribute): unexpected scenarios cause breaking change
jaredcnance
added a commit
that referenced
this issue
Jul 5, 2018
specify symbols server for develop
v3.0.0-beta NotesWe need help from you: if you’re interested in helping get this feature fully released, download the 3.0.0-beta version(s) and provide feedback in this issue or you can open a new issue for bug reports. Thanks!! Public Resource Name Resolution
[Resource("models"] public class Model : Identifiable { /* ... */ }
[Resource("models")] public DbSet<Model> Models { get; set; }
TODO
Known Bug List
|
jaredcnance
added a commit
that referenced
this issue
Aug 13, 2018
jaredcnance
added a commit
that referenced
this issue
Aug 13, 2018
fix(#241): TypeLocator bug -- add tests
milosloub
pushed a commit
to milosloub/JsonApiDotNetCore
that referenced
this issue
Sep 24, 2018
…-api-dotnet#241-2 Auto Resource/Service Discovery
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should be able to reflect on the assembly and auto discover all implementations of
IIdentifiable<,>
,IResourceService<,>
,IEntityRepository<,>
adding them to theContextGraph
. A possible API might look like:We may also expose the following for finer control:
This work may include improved handling for multiple database contexts. See #269. In order to automatically handle multiple contexts, we need a way to specify that
FooRepository
depends onBarDbContextResolver
at startup. Currently, I don't think Microsoft's DI library provides anything with that level of registration. We could consider providing a separate package that depends on Autofac (for example) where we explicitly construct the dependency graph.The text was updated successfully, but these errors were encountered: