Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce OpenFeature.Extensions.Hosting package #264

Open
austindrenski opened this issue Jan 8, 2024 · 0 comments · May be fixed by #181
Open

Introduce OpenFeature.Extensions.Hosting package #264

austindrenski opened this issue Jan 8, 2024 · 0 comments · May be fixed by #181
Assignees
Labels
enhancement New feature or request

Comments

@austindrenski
Copy link
Member

austindrenski commented Jan 8, 2024

I'm eventually planning to offer this upstream as part of a new OpenFeature.Extensions.Hosting package à la OpenTelemetry.Extensions.Hosting, but still working through the realistic use cases and general ergonomics, but just mentioning that so this doesn't seem entirely irrelevant to the project at hand.

This has been suggested before, and I think it's a good idea. I would welcome such a PR, or at least an issue proposing it.

I'll open a new issue to track this, and will see about getting a draft PR put together over the next couple of weeks.

Originally posted by @austindrenski in open-feature/dotnet-sdk-contrib#125 (comment)

austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
but tldr; libraries don't need the implementation package, so reduce
to the abstractions package to remove transitive dependencies on:

- Microsoft.Extensions.DependencyInjection
- Microsoft.Extensions.Options
- (and a few others depending on the TFM)

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
but tldr; libraries don't need the implementation package, so reduce
to the abstractions package to remove transitive dependencies on:

- Microsoft.Extensions.DependencyInjection
- Microsoft.Extensions.Options
- (and a few others depending on the TFM)

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
and tldr; if there's more than one project under `src/`, having the
`<PackageId>` hard-coded in `build/Common.prod.props` causes MSBuild
to panic.

There are two options to fix this:

1. ```diff
   - <PackageId>OpenFeature</PackageId>
   + <PackageId>$(MSBuildProjectName)</PackageId>
   ```
2. ```diff
   - <PackageId>OpenFeature</PackageId>
   ```

Since NuGet defaults `PackageId` to the assembly name, I'm opting
for (2), but if I've overlooked some nuance/custom build steps that
require setting `PackageId` explicitly, then we could just as well
fallback to (1).

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
but tldr; libraries don't need the implementation package, so reduce
to the abstractions package to remove transitive dependencies on:

- Microsoft.Extensions.DependencyInjection
- Microsoft.Extensions.Options
- (and a few others depending on the TFM)

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
and tldr; if there's more than one project under `src/`, having the
`<PackageId>` hard-coded in `build/Common.prod.props` causes MSBuild
to panic.

There are two options to fix this:

1. ```diff
   - <PackageId>OpenFeature</PackageId>
   + <PackageId>$(MSBuildProjectName)</PackageId>
   ```
2. ```diff
   - <PackageId>OpenFeature</PackageId>
   ```

Since NuGet defaults `PackageId` to the assembly name, I'm opting
for (2), but if I've overlooked some nuance/custom build steps that
require setting `PackageId` explicitly, then we could just as well
fallback to (1).

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
and tldr; if there's more than one project under `src/`, having the
`<PackageId>` hard-coded in `build/Common.prod.props` causes MSBuild
to panic.

There are two options to fix this:

1. ```diff
   - <PackageId>OpenFeature</PackageId>
   + <PackageId>$(MSBuildProjectName)</PackageId>
   ```
2. ```diff
   - <PackageId>OpenFeature</PackageId>
   ```

Since NuGet defaults `PackageId` to the assembly name, I'm opting
for (2), but if I've overlooked some nuance/custom build steps that
require setting `PackageId` explicitly, then we could just as well
fallback to (1).

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
and tldr; if there's more than one project under `src/`, having the
`<PackageId>` hard-coded in `build/Common.prod.props` causes MSBuild
to panic.

There are two options to fix this:

1. ```diff
   - <PackageId>OpenFeature</PackageId>
   + <PackageId>$(MSBuildProjectName)</PackageId>
   ```
2. ```diff
   - <PackageId>OpenFeature</PackageId>
   ```

Since NuGet defaults `PackageId` to the assembly name, I'm opting
for (2), but if I've overlooked some nuance/custom build steps that
require setting `PackageId` explicitly, then we could just as well
fallback to (1).

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
@austindrenski austindrenski linked a pull request Jan 16, 2024 that will close this issue
10 tasks
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 16, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 17, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 17, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 17, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 17, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 19, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 19, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
and tldr; if there's more than one project under `src/`, having the
`<PackageId>` hard-coded in `build/Common.prod.props` causes MSBuild
to panic.

There are two options to fix this:

1. ```diff
   - <PackageId>OpenFeature</PackageId>
   + <PackageId>$(MSBuildProjectName)</PackageId>
   ```
2. ```diff
   - <PackageId>OpenFeature</PackageId>
   ```

Since NuGet defaults `PackageId` to the assembly name, I'm opting
for (2), but if I've overlooked some nuance/custom build steps that
require setting `PackageId` explicitly, then we could just as well
fallback to (1).

Signed-off-by: Austin Drenski <austin@austindrenski.io>
toddbaert referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 19, 2024
Ran across this while working on open-feature/dotnet-sdk-contrib#127,
and tldr; if there's more than one project under `src/`, having the
`<PackageId>` hard-coded in `build/Common.prod.props` causes MSBuild
to panic.

There are two options to fix this:

1. ```diff
   - <PackageId>OpenFeature</PackageId>
   + <PackageId>$(MSBuildProjectName)</PackageId>
   ```
2. ```diff
   - <PackageId>OpenFeature</PackageId>
   ```

Since NuGet defaults `PackageId` to the assembly name, I'm opting
for (2), but if I've overlooked some nuance/custom build steps that
require setting `PackageId` explicitly, then we could just as well
fallback to (1).

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 20, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 22, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 23, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 23, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 23, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 23, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 23, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 27, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 27, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 27, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
austindrenski referenced this issue in austindrenski/open-feature-dotnet-sdk Jan 29, 2024
See: open-feature/dotnet-sdk-contrib#127

Signed-off-by: Austin Drenski <austin@austindrenski.io>
@askpt askpt transferred this issue from open-feature/dotnet-sdk-contrib Apr 24, 2024
@askpt askpt added the enhancement New feature or request label Apr 24, 2024
@askpt askpt added this to the 2.0 (breaking) milestone Apr 24, 2024
@askpt askpt self-assigned this Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants