Azure / Azure/monaco-kusto

Lazy loading of schema

Open
#453 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
84
Forks
36
PR merge metrics
No merged PRs in 30d

Description

Does this plugin allow for a more lazy , two step strategy for loading the schema, where we provide it only index names first, and then when the user has typed the index name, we are asked for that index's schema? I have a use-case where I have 40-50 tables in my database and each table could potentially have thousands of columns, therefore setting the entire schema in one go could generate extremely large payloads. Is there a way to get around this?

Thanks!

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by reviewing the plugin's existing schema-loading API and determine whether it can provide index names before requesting an index's schema; done means supporting the two-step loading flow without sending the entire schema payload up front.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.