Prior to this change, if an end user opened a package in VS Code and the following were true:
the file that was opened was not the crossplane.yaml
the end user did not have external dependencies loaded in their cache as defined by the crossplane.yaml
There would be no feedback given to the end user. Nothing.
With this change, we now validate the crossplane.yaml during the initialization stage and emit diagnostics async so that if the above occurs, the end user will see their crossplane.yaml file turn red and a notice will show up in the problems window.
[X] Run make reviewable to ensure this PR is ready for review.
How has this code been tested
Verified that the expected behavior occurred when working with an empty cache and the file that was open during initialization was not the crossplane.yaml.
Description of your changes
Prior to this change, if an end user opened a package in VS Code and the following were true:
crossplane.yamlThere would be no feedback given to the end user. Nothing.
With this change, we now validate the
crossplane.yamlduring the initialization stage and emit diagnostics async so that if the above occurs, the end user will see theircrossplane.yamlfile turn red and a notice will show up in the problems window.Fixes #136
I have:
make reviewableto ensure this PR is ready for review.How has this code been tested
Verified that the expected behavior occurred when working with an empty cache and the file that was open during initialization was not the
crossplane.yaml.