Why is provideVSCodeDesignSystem() necessary?

[justinfagnani]

Feature request

Provide easier to use component definitions, either self-registering modules or modules that export a custom element class to register.

Expected behavior

Elements are easier to use.

Current behavior

Elements require an unusual boilerplate to start using:

This is the first time I've used anything based on Fast, but I couldn't get any elements to render at first, then noticed this in the docs:

import { provideVSCodeDesignSystem, vsCodeButton } from "@vscode/webview-ui-toolkit";

provideVSCodeDesignSystem().register(vsCodeButton());

As a user this seems like uneccessary boilerplate. Why can't I just import the library and use the components? Like:

import "@vscode/webview-ui-toolkit";

This is how most web components that I use behave.

[hawkticehurst]

Hey @justinfagnani!

I completely agree. This API/syntax is an artifact of how the current version of FAST works. The next major release of FAST should have an import syntax that looks closer to what you suggested.

cc @chrisdholt for further details about what the future API will look like and current timelines on the release date

[chrisdholt]

Hey @justinfagnani!

I completely agree. This API/syntax is an artifact of how the current version of FAST works. The next major release of FAST should have an import syntax that looks closer to what you suggested.

cc @chrisdholt for further details about what the future API will look like and current timelines on the release date

Future syntax is just that - the other was an artifact of a different era for "reasons". @hawkticehurst I'll reach out offline as I owe you actual code pertaining to this. With @justinfagnani's ask, I'll prioritize it best I can :)