microsoft / microsoft/FeatureManagement-Dotnet
SessionManager does not work when FeatureDefinition is null
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 129
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
We use a ISessionManager to maintain a consistent flag state across child requests. If somewhere is no FeatureDefinition, the result of checking the flag in one service may differ from the result in another within the same logical operation.
The behavior changed in version 4 of the package.
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 tracing ISessionManager behavior when FeatureDefinition is null and compare flag checks across child requests within one logical operation. Reproduce the inconsistent results described for version 4, then verify that the session preserves a consistent flag state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100