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

Bump version to 3.1.1 & Adjust title level in README #329

Merged
merged 7 commits into from
Dec 13, 2023

Conversation

zhiyuanliang-ms
Copy link
Contributor

No description provided.

README.md Outdated
@@ -141,7 +144,7 @@ A `RequirementType` of `All` changes the traversal. First, if there are no filte

In the above example, `FeatureW` specifies a `RequirementType` of `All`, meaning all of it's filters must evaluate to true for the feature to be enabled. In this case, the feature will be enabled for 50% of users during the specified time window.

### Service Registration
## Service Registration
Copy link
Member

@jimmyca15 jimmyca15 Dec 7, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the root title should be Consumption and then it goes over featureManager.IsEnabledAsync right away.

Then it Service Registration, and DI can be following subsections.

Feature check section would no longer be needed.

And I'd suggest moving the scoped services section last in the Consumption parent section.

So

Consumption (Immediate text replaces feature check section)

  • Service Registration
  • Dependency Injection
  • Scoped Feature Management Services

README.md Outdated
@@ -439,7 +447,7 @@ public void ConfigureServices(IServiceCollection services)
**Advanced:** `IHttpContextAccessor`/`HttpContext` should not be used in the Razor components of server-side Blazor apps. [The recommended approach](https://learn.microsoft.com/en-us/aspnet/core/blazor/security/server/interactive-server-side-rendering?view=aspnetcore-7.0#ihttpcontextaccessorhttpcontext-in-razor-components) for passing http context in Blazor apps is to copy the data into a scoped service. For Blazor apps, `AddScopedFeatureManagement` should be used to register the feature management services.
Please refer to the `Scoped Feature Management Services` section for more details.

## Providing a Context For Feature Evaluation
### Providing a Context For Feature Evaluation
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't consider this a subsection of implementing a filter.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And perhaps the built-in filters section should be promoted a level.

@zhiyuanliang-ms zhiyuanliang-ms force-pushed the zhiyuanliang/adjust-readme-title-level branch from 76da523 to 2697fa8 Compare December 13, 2023 03:20
@zhiyuanliang-ms zhiyuanliang-ms merged commit 07e4d29 into main Dec 13, 2023
2 checks passed
@zhiyuanliang-ms zhiyuanliang-ms deleted the zhiyuanliang/adjust-readme-title-level branch December 13, 2023 05:55
@zhiyuanliang-ms zhiyuanliang-ms changed the title Adjust title level in README Bump version to 3.1.1 & Adjust title level in README Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants