Open jamest-gaia opened 1 year ago
Hi @jamest-gaia Thanks for opening this issue. I can see how that would improve your ability to address the error. I suppose the current approach is an attempt to limit the size of log lines for resources with a large number of arguments. I suppose its a trade-off between these two usability cases, but it's possible we haven't struck the perfect balance here.
@RobbieMcKinstry A few ideas for the improvement since there's no native YAML completion.
--verbose
flag so the full list of properties is displayed?--verbose
to increase the properties visibilityThanks @aureq , having --verbose
(and being guided to use it) would be very satisfactory to me.
Also, a visual indication or grouping of required vs optional properties would also be very helpful.
Hello!
Issue details
When I'm developing something in AWS Crosswalk using YAML it would save me a bunch of time if I could see the available properties right in the error message. See screenshot![image](https://github.com/pulumi/pulumi-yaml/assets/129140151/0f9aebe0-efa2-4b30-907d-d3c2cccfa9b7)
Affected area/feature