Change how VmValueRenderer renders Typed values #1412
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.
This addresses an issue where rendered values can be ambiguous. For example, a module gets rendered as
new ModuleClass {}. Also, a class gets rendered asnew Person {}, without specifying where that class comes from.This changes it to render the qualified name instead of the simple name.
#pkl:basedoes not changeFor example:
new k8s.core.v1.Service {}instead ofnew ModuleClass {}.new k8s.core.v1.Service#ServiceSpec {}instead ofnew ServiceSpec {}new pkl.Project {}instead ofnew ModuleClass {}This affects the following:
toString()trace()