[Sight.IoC] Make exception messages clearer for debugging
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
If a type cannot be resolved we need to know why, what dependency cannot be resolved, etc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Sight.IoC type-resolution and dependency-resolution paths, then reproduce an unresolved type or dependency to see the current exception output. Done means the exceptions identify what could not be resolved and why, with tests covering the clearer messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100