Description of changes
When following the getting started guide, I got stuck because esbuild seems to prefer the UMD exports of some transpiled modules. Those can not be statically analyzed and cause runtime errors for missing dependencies - in my case `vscode-json-languageservice` and some of its dependencies.
By telling esbuild to prefer the module field over main, this issue gets avoided.
Description of changes
Updates the getting started guide to include new content on how to:
- Avoid loading the toolkit package directly from node_modules
- Register the toolkit components in JS/TS
- Add proper content security policies for loading scripts, styles, and images
Description of changes
Updates the main readme.md and getting-started.md resource links.
- Adds a link to the VS Code webview UX guidelines
- Simplifies the naming of other VS Code webview doc links
- Removes the Storybook link in anticipation of removing Storybook
Description of changes
Updates a code snippet from the getting started guide that demonstrated an improper way of disposing of webview panel resources when the panel is closed.
Description of changes
Pulls in an upstream change from FAST Foundation that resolves an issue where some of the React toolkit components were forced to use enums when defining a handful of attribute values.
This fix now allows all React components to use literal string values when defining attributes.
Also updates the React component docs to reflect this change.
Description of changes
This PR contains a variety of minor tweaks and changes to the entire toolkit project. The changes include:
- Updates to the GitHub templates
- Updates to Storybook config
- Updates to our contributing guidelines
- Updates to the project README
- Updates to the getting started guide
- Add a copyright notice to various source code files
Description of changes
This is a temporary stop-gap solution to this [upstream issue](https://github.com/microsoft/fast/issues/5494) where a handful of toolkit component attributes (when wrapped as React components) will result in TS type errors because the attributes/props require an enum as the value.
Once the upstream issue is resolved these changes should be reverted.
Description of changes
Fixes an issue with component registration functions where type information was being lost in certain cases.
This caused downstream problems when used with the `fast-react-wrapper` so that component attributes had incomplete type info and rendered the component unusable in TypeScript-based React projects.
Description of changes
- Lock typescript and api extractor file versions due to typescript conflicts
- Add tsconfig to enable eslint
- Remove introduction storybook doc
- Add eslint as dev dependency for lint step
- Update prettier config
Description of changes
Includes various updates to the toolkit documentation.
Adds a link to the Webview API docs in the toolkit README description
Removes code comments from getting started guide code blocks
Add file path comments to each code block
Description of changes
Update the getting started guide to reflect the major [changes](https://github.com/microsoft/vscode-webview-ui-toolkit-samples/pull/20) made to the Hello World sample extension.
Also update `README.md` to present the toolkit npm install command more prominently to readers.
Description of changes
In prep for public release, removing the `vscode-number-field` since it has some outstanding accessibility/functionality issues.
Description of changes
Remove and update the following components that need more time and exploration in prep for public release.
- Remove Breadcrumb / Breadcrumb Item
- Remove Combobox
- Remove Progress Bar
- Update Badge
Description of changes
Since the implementation of the Anchored component has been pushed back to July/August, temporarily removing the Menu and Menu Item components in preparation for the private beta.
Description of changes
- Update primary background design token default value with the correct color
- Add primary and secondary design tokens
- Add appearance attribute to Badge
- Update Storybook docs to reflect changes
Update the following NPM scripts to match the conventions used by other scripts and/or increase the clarity of the scripts.
- `npm run build:storybook` --> `npm run build:docs`
- `npm run deploy:storybook` --> `npm run deploy:docs`
- `npm run fmt:check` --> `npm run fmt`
- `npm run fmt` --> `npm run fmt:fix`
- `npm run test:coverage` --> `npm run test`
- Add TSDoc comments for all instances of the `connectedCallback` method used in component classes.
- Remove unused parameters from `defaultSlottedContentChanged` method
- Regenerate API report
Set up the `npm run deploy:storybook` script to deploy the Storybook documentation site to GitHub Pages.
Additionally, update all the documentation links to point to the new deployment URL.
Adopted the new FAST Foundation Design Tokens API.
- Created new `design-tokens.ts` file
- Removed `design-system.ts` and Design System Provider code
- Updated all components to consume new tokens
- Updated `applyTheme.ts` utility to use new API
Clean up documentation a bit by:
- Updating README and Storybook intro value prop bullet points
- Fix broken link in the Getting Started guide
- Update `components.md` to reflect tabs to panels component name change
AlCalzone
Hawk Ticehurst
David Dossett
Chris Holt