Bump System.Linq.Dynamic.Core from 1.6.0 to 1.7.3 - #51
Closed
dependabot[bot] wants to merge 242 commits into
Closed
Conversation
The background cleanup task used while(true) with no way to stop it during application shutdown. Now uses CancellationTokenSource that gets cancelled on Dispose(), allowing graceful shutdown. Closes #26
- Add GitHub Actions build and test workflow - Add bug report and feature request issue templates - Add pull request template - Add GitHub Sponsors funding configuration - Improve .gitignore for better development experience
Add CI/CD pipeline and project configuration
…iddleware (closes #17)
…cross requests (closes #16)
…ernal services (closes #19)
…size recommendations (closes #20)
- Add FlagEvaluationLog model (flagName, userId, result, timestamp, reason) - Add IFlagEvaluationLogService interface and in-memory FlagEvaluationLogService - Add EnableAuditLog opt-in property to FeatureFlagOptions (default: false) - Record FlagEvaluationLog in FeatureFlagService.IsEnabledAsync with reason - Register FlagEvaluationLogService as singleton in DI - Update FeatureFlagServiceTests to supply new constructor dependencies
Add comprehensive unit tests for AuditLogService, GradualRolloutSchedulerService, and FlagEvaluationLogService. Tests cover: - Audit log retrieval and filtering by user, flag, and pagination - Scheduled rollout processing and advancement with error handling - Flag evaluation tracking and metrics aggregation - Edge cases, null handling, and error conditions
Add integration tests for full feature flag workflows and WebhookService operations: - End-to-end flag evaluation scenarios (enable/disable, percentage rollout) - Rule-based targeting with AND/OR condition logic - Distribution accuracy for percentage allocations across users - Concurrent evaluation thread safety - Custom attribute support in rule evaluation - A/B testing variant assignment - Webhook registration, validation, and event triggering
Update xunit.runner.visualstudio to 3.0.0 and Moq to 4.20.72 for compatibility with available packages on NuGet.
…with tests - Unseal FeatureFlagDbContext and HttpApiClient and mark overridable members virtual; sealing them broke every consumer that extends these seams - Validate webhook URL format in RegisterWebhookAsync and throw ArgumentException for malformed addresses - IsValidEmail returns false for null input instead of throwing - XmlExporter serializes IsEnabled via bool.ToString for stable casing - Add GetAllActiveWebhooksAsync to IWebhookService for unfiltered listing
…listing - Numeric rule conditions and conversion utilities parse with InvariantCulture so evaluation does not depend on server locale - XML parser reads ids and timestamps with InvariantCulture and round-trip DateTime handling - Rate limiting middleware sets headers via the indexer instead of Add, synchronizes access to per-client timestamp queues, and uses the configured window in GetRemainingRequests instead of a hardcoded value - AdminController.GetWebhooks returns actual registered webhooks instead of an always-empty list; uptime formatting uses invariant culture
…onTestsExtensions
…n to RuleEvaluationServiceTestsExtensions - Add ArgumentNullException.ThrowIfNull guard clauses to all public methods - Add comprehensive <exception> tags to XML documentation for every throw case - Improve <param> documentation precision and consistency - Fix typo in AssertRuleResultAsync parameter documentation (actual -> actualTask) - Maintain all existing public API signatures and behavior
…iceTestExampleExtensions
…Enabled, and HasRules methods. Co-authored-by: aider (groq/llama-3.1-8b-instant) <aider@aider.chat>
Co-authored-by: aider (groq/llama-3.1-8b-instant) <aider@aider.chat>
Okay, let me go through the user's request step by step. They want me to generate a commit message for the changes made to the ValidationExceptionExtensions.cs file. The commit message needs to follow the conventional commits style, which means using a type prefix like docs, feat, fix, etc., followed by a concise description. First, I need to determine the type of the commit. The user added XML documentation comments, which is related to documentation. So the type should be "docs". The scope is "exceptions" because the file is in the Exceptions namespace and deals with ValidationException. The description should summarize the change, which is adding XML documentation to the ValidationExceptionExtensions class and its methods. Looking at the diffs provided, the changes are all about adding or enhancing the XML comments. The user emphasized that no code logic was changed, only documentation. So the commit message should reflect that it's a documentation update. The conventional commit type for documentation changes is "docs". Next, I need to make sure the message is in the imperative mood. The correct format would be "docs(exceptions): add XML documentation to ValidationExceptionExtensions". This follows the structure <type>(<scope>): <description>, which is standard for conventional commits. I should also check the length. The message should not exceed 72 characters. Let me count: "docs(exceptions): add XML documentation to ValidationExceptionExtensions" – that's 70 characters, which is within the limit. No other types like feat or fix are appropriate here since there's no new feature or bug fix. The user specifically mentioned adding documentation, so "docs" is the right choice. The scope "exceptions" helps narrow down where the documentation was added. I need to ensure that the commit message doesn't mention any other changes, like tests or code modifications, which weren't part of this task. The user also warned against violating hard rules like touching other files, which the commit message doesn't address. Finally, confirming that the message accurately reflects the changes made. The added XML comments in the three methods (HasErrors, GetErrorMessage, ToFlattenedErrorDictionary) are all covered under the description. The message is concise, specific, and follows the required format. </think> ``` docs(exceptions): add XML documentation to ValidationExceptionExtensions ``` Co-authored-by: aider (groq/qwen/qwen3-32b) <aider@aider.chat>
…th usage examples
--- updated-dependencies: - dependency-name: System.Linq.Dynamic.Core dependency-version: 1.7.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/nuget/src/FeatureFlags/System.Linq.Dynamic.Core-1.7.3
branch
July 16, 2026 05:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated System.Linq.Dynamic.Core from 1.6.0 to 1.7.3.
Release notes
Sourced from System.Linq.Dynamic.Core's releases.
1.7.3
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.7.2...v1.7.3
1.7.2
What's Changed
New Contributors
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.7.1...v1.7.2
1.7.1
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.7.0...v1.7.1
1.7.0
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.10...v1.7.0
1.6.10
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.9...v1.6.10
1.6.9
What's Changed
New Contributors
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.8...v1.6.9
1.6.8
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@1.6.7...v1.6.8
1.6.6
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.5...v1.6.6
1.6.5
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.4...v1.6.5
1.6.4
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.3...v1.6.4
1.6.3
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.2...v1.6.3
1.6.2
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.0.2...v1.6.2
1.6.0.2
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.0.1...v1.6.0.2
1.6.0.1
What's Changed
Full Changelog: zzzprojects/System.Linq.Dynamic.Core@v1.6.0...v1.6.0.1
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)