Conversation
| return rootConfigSchemaUri; | ||
| } | ||
| return undefined; | ||
| }, |
There was a problem hiding this comment.
@kartikgupta-db Is this registration updated as new bundle configuration files are added, or does this only trigger on extension reload? Not clear to me when this contributor callback is called.
There was a problem hiding this comment.
It is called everytime a new yaml file is opened/created .The file list update happens only when root file is changed. This is wrong. The fix is here #922
| } | ||
| if ( | ||
| bundleFileList.find( | ||
| (i) => i.fsPath === Uri.parse(resource).fsPath |
There was a problem hiding this comment.
This can call Uri.parse outside of the lambda to save some cycles.
| ) | ||
| ).map((i) => Uri.file(i)); | ||
| } | ||
| } |
There was a problem hiding this comment.
Checking: this will soon use the bundle validate equivalent output to determine the same, correct?
There was a problem hiding this comment.
yes. I have tried to design it to be easily swappable.
Changes
databricks bundle schemacommand) to provide typing for the parsed bundle object.NOTE: This PR currently parses yamls in code. We want to move that to databricks CLI. The implementation can is modular and can be swapped with the CLI calls once we have those features in the CLI.
Tests