Comments (5)
Thanks for looking into this @markphillips100. I never faced the issue myself but always suspected it was there.
Would it be interesting to have an extension point before each handler invocation? The extension point could expose the service provider and allow the creation of a child scope for each handler if needed.
from servicecomposer.aspnetcore.
Not sure that it's needed, or more specifically, something that this lib should provide and best left for developers to supply it themselves as required.
For example, I tend to have small handlers which pass a request type to a mediator. The implementation of those mediator commands can inject IServiceProvider if they require it. So in my case having the handler be supplied IServiceProvider would end up not being used as mediator wouldn't (cannot) use it directly.
I guess I just wanted to maybe surface it in documentation perhaps that developers should be aware of the thread safety being imposed is all. Just a note perhaps, what do you think?
from servicecomposer.aspnetcore.
Makes sense to at least provide some documentation. I'll craft it. Thanks.
from servicecomposer.aspnetcore.
Raised #371. @markphillips100 can you have a look?
from servicecomposer.aspnetcore.
Looks good @mauroservienti
from servicecomposer.aspnetcore.
Related Issues (20)
- Add IConfiguration to ViewModelCompositionOptions HOT 8
- Dealing with exception handling from ViewModelAppenders inside a composition HOT 1
- Question: Any thoughts on where composition should occur when using Blazor? HOT 16
- Question: Thoughts on integrating viewmodel composition output with signalr? HOT 13
- Is the HTTP attribute needed for subscribers?
- Make EnableWriteSupport() the default behavior
- Scatter/Gather support
- Test if it works when trimming and using native AOT in .NET 8
- EndpointScopedViewModelFactory not found HOT 4
- Investigate the IEndpointMetadataProvider interface and its usage in generating documentation (former Swagger)
- Investigate how to get rid of Json.Net and use System.Text.Json
- Drop EnableWriteSupport in v4.0.0
- Obsolete EnableWriteSupport with an error
- Target only .NET 8
- Remove MapCompositionHandlers(this IEndpointRouteBuilder endpoints, bool enableWriteSupport)
- When write support is disabled provide a better error than 404
- Add .NET 8 as a target framework
- Make model bind throw on binding errors, with an option to disable
- Better visualizations using OpenTelemetry
- Remove the requirement for Http* attributes for subscribers
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from servicecomposer.aspnetcore.