Skip to content

Conversation

@RafeArnold
Copy link
Contributor

allowing more useful help messages upon transform failure.

implementation of #619

  • add location property to ValueSource.Invocation
  • add location to MapValueSource invocations.
  • add location to JsonValueSource invocations.

@RafeArnold
Copy link
Contributor Author

i think the ability to construct the location string lazily would be useful, as it's only used for the unhappy path of parsing and could potentially require more complex computation for some value sources. i havent implemented this functionality here because it would require OptionInvocation and OptionCallTransformContext to also allow lazy name properties which may have backwards compatibility concerns. i can have a crack at that additional work if it would be useful.

allowing more useful help messages upon transform failure.
to demonstrate more complex invocation locations.
@RafeArnold RafeArnold force-pushed the value-source-location-property branch from 61ab667 to bd9bd79 Compare November 10, 2025 09:46
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.

1 participant