Repository navigation
Format error messages recursively for nested child rules and ignore object cycles - #757
Open
Martin Brekhof (MBrekhof) wants to merge 1 commit into
Conversation
Contributor
|
Martin Brekhof (@MBrekhof) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
This branch has not been deployed
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
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.
Problem
Nested
ChildResultserror messages are never formatted:RulesEngine.ExecuteAllRulesAsynconly runsFormatErrorMessageson top-levelRuleResultTreeitems where!result.IsSuccess. Any failed child rules insideresult.ChildResultsretain literal$(Property)placeholders inChildResults[*].ExceptionMessage.Object graph cycles throw
JsonExceptionduring error formatting:When
IgnoreExceptionisfalse(default) and an input object has a bidirectional navigation property (e.g., EF Core parent/child entities),JsonSerializer.Serialize(input.Value)insideFormatErrorMessagesthrowsSystem.Text.Json.JsonException: A possible object cycle was detected.Solution
result.ChildResultswhen formatting error messages on failed rule trees.JsonSerializerOptions { ReferenceHandler = ReferenceHandler.IgnoreCycles }toJsonSerializer.SerializeinFormatErrorMessages.test/RulesEngine.UnitTest/FormatErrorMessagesNestedAndCyclesTest.cs.