Schema is not updated when using the same name
- Dominant language
- TypeScript
- Stars
- 84
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
### Description
When setting the schema with `setSchemaFromShowSchema()` the schema is not updated in the kusto worker if the schema uses the same name as before.
### Steps to Reproduce
1. set a schema with name 'Default' with `setSchemaFromShowSchema()`
2. Update the schema with name 'Default' with new OrderedColumns of a table
3. Run `setSchemaFromShowSchema()` again with the updated schema
4. Schema is not updated!
```
monaco.languages.kusto.getKustoWorker().then(workerAccessor => {
const model = this.editor.getModel();
workerAccessor(model.uri).then(worker => {
worker.setSchemaFromShowSchema(schema, '', name);
});
});
```
**Expected behavior:** I expect that the schema is updated with the new columns
**Actual behavior:** Schema is not upedated
**Reproduces how often:** 100%
### System configuration
monaco-kusto version: 10.0.4
monaco-editor version: ^0.37.1
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the issue through the Kusto worker's setSchemaFromShowSchema() call, using the two schemas described in the steps. Trace how the worker handles a schema named Default when its OrderedColumns change, then verify that a second call exposes the updated columns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100