Azure / Azure/azure-functions-openapi-extension
Package for isolated workers use in-process nuget packages
- Dominant language
- C#
- Stars
- 388
- Forks
- 202
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the issue**
When I tried to add OpenAPI for isolated workers (`Microsoft.Azure.Functions.Worker.Extensions.OpenApi` version 1.5.1)
that package had reference to `Microsoft.Azure.WebJobs.Extensions.OpenApi.Core`
and this one have references to:
```
Microsoft.Azure.WebJobs.Extensions.Http
Microsoft.Azure.WebJobs.Extensions.OpenApi.Configuration.AppSettings
```
They are packages to in-process workers, and should not be used for isolated workers.
The issue also provide miss used attributes, that should be use from isolated workers, but it's taken a in-process
**To Reproduce**
Just add `Microsoft.Azure.Functions.Worker.Extensions.OpenApi` into your project
**Expected behavior**
OpenAPI should not use references from different type of the applications
so isolated workers should only used isolated packages (`Microsoft.Azure.Functions.Worker.*`)
and in-process workers should only use in-process packages (`Microsoft.Azure.WebJobs.*`)
**Screenshots**

Contributor guide
Research direction
Start by adding Microsoft.Azure.Functions.Worker.Extensions.OpenApi version 1.5.1 to an isolated-worker project and inspect its package dependency graph. Compare the referenced Microsoft.Azure.WebJobs.* and Microsoft.Azure.Functions.Worker.* packages against the issue's expected behavior; done means isolated workers no longer receive in-process package references or attributes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, openapi
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100