This repository was archived by the owner on Jan 5, 2026. It is now read-only.
Adding intellisense to uiSchema #6047
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes microsoft/BotFramework-Composer#4186
Proposed Changes
In R10, we introduced Intellisense to Composer fields.
For this first release, the mappings between components and valid Intellisense scopes* were hardcoded.
*Scopes refer to the type of results that Intellisense returns, such as "user-variables".
In R11, we would like to have the uiSchema dictates this mapping.
Below is a screenshot of how overwriting the uiSchema enables custom Intellisense scopes.
