Comments (1)
Thanks for your question @Stephanvs and I'm happy that you're thinking about using ServiceComposer.
I spent a lot thinking about exception handling and less important handlers and I couldn't find a solution that satisfied me without compromising on something. I'm leaning toward thinking that it's not ServiceComposer composer responsibility to deal with errors in handlers.
Let me give you an overview of the whys:
- ServiceComposer composer has a generic ICompositionErrorsHandler mechanism that allows code to hook into error handling, and intentionally doesn't allow for error suppression, it's just a way to provide handlers with a chance to recover. This is primarily designed with write scenarios in mind and not read ones.
- If ServiceComposer was to handle exceptions for each handler it would also require a mechanism to let handlers explain if the error should bubble up or not, otherwise the only option would be to suppress any error which is not ideal.
Given that your code is the best place to understand if an error should bubble up or not, I have always preferred to have try/catch blocks in handlers where appropriate, instead of a generic mechanism to handle failing handlers.
That being said. Change my mind! 😎😀
from servicecomposer.aspnetcore.
Related Issues (20)
- Add IConfiguration to ViewModelCompositionOptions HOT 8
- 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.