Azure / Azure/azure-functions-host
Fix ScriptHost resolution in ScriptRouteHandler
Open
area: engineering
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 36
Description
The ScriptHost is currently resolved using the ScriptHostManager static instance property. This should be improved to avoid many issues caused by that pattern today.
This work item has a dependency on the DI enhancements we'll be landing.
Contributor guide
Research direction
Locate ScriptRouteHandler and inspect how it currently obtains ScriptHost through the ScriptHostManager static instance property. Read the related DI enhancements when available and determine the intended injection boundary. Done means ScriptHost resolution no longer depends on that static instance and the existing handler behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100