Extensibility: making it easy to register additional services on the internal service provider

Open
#8,710 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
databases

Research direction

Start by examining the OnConfiguring entry point and the existing ReplaceService API described in the issue. Trace how EF Core manages its internal service provider and ILoggerFactory, then determine how additional implementations could coexist with existing services. Done means an API can register supported additional service implementations without removing existing ones.

Written by the indexing model from the issue text.

Description

area-dbcontext

Consider an API that users can invoke in OnConfiguring() to provide additional service implementations of service types for which EF Core (or providers) support multiple instances. This is similar to ReplaceService but without removing existing implementations.

One example of where this could have been useful is adding additional logging providers using the DI-based mechanisms enabled in 2.0 (https://github.com/aspnet/Logging/issues/346) when EF Core manages the ILoggerFactory in the internal service provider.

Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.