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

ParameterCapturing: Remove quotes from string evaluations, include failure reason information make the value nullable #6548

Conversation

clguiman
Copy link
Contributor

@clguiman clguiman commented Apr 29, 2024

Summary
  • Updated the captured parameter result so the value parameter and activity id are nullable strings.
  • Introduced ObjectFormatterResult which includes the evaluated and formatted parameter value and evaluation metadata flags (IsNull, FailedEval, UnsupportedEval, EvalHasSideEffects). `ObjectFormatter now returns objects of the new type.
  • EventSourceEmittingProbes.EnterProbe doesn't request adding quotes to the formatted value anymore. The quotes were added to easily parse the ILogger output, but we don't have that problem anymore.
  • Updated ParameterCapturingEventSource to send the new evaluation flags as part of the captured paramater.
  • Updated WebApi.Models.CapturedParameter to include a new optional property: EvalFailReason.
  • Updated the formatter tests to support the new behavior.
Release Notes Entry

@clguiman clguiman requested a review from a team as a code owner April 29, 2024 18:18
@clguiman clguiman changed the title ParameterCapturing: Remove quotes from string evaluations, include failure reason information and IsNull flag ParameterCapturing: Remove quotes from string evaluations, include failure reason information make the value nullable May 3, 2024
- Remove ObjectFormatterResult.Empty
- Rename ParameterEvaluationFlags to ParameterEvaluationResult and convert it from an enum of flags to mutually exclusive enum values.
- Update ObjectFormatter to default EvalResult to Success.
@schmittjoseph schmittjoseph merged commit 6bfb28d into dotnet:main May 9, 2024
28 checks passed
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.

3 participants