The optional parameters are only necessary for caching and we do not want to cache our websites from the application layer. Caching will continue to occur from Azure Front Door service.
Co-authored-by: Chris Holt <chhol@microsoft.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change removes the FAST Creator application and the FAST tooling examples site. @awentzel there may be some pipeline changes that should be made so that the Creator is not automatically deployed during PR merge, can you confirm? I have removed the `.yml` file.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change makes the following style updates:
- updates the width of the panes to 300px to allow:
- The color picker overlay to display without clipping
- The fast-tabs to display without clipping
- updates the width of the select to be as minimal as the longest piece of text content will allow
- updates the overflow on several elements where it was unneeded
- updates the form component to be display flex without relying on an outside element to set it
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Creator and Explore apps after building the project and test the desktop and mobile views to see the changes.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* add fluent svg icons package to fast-website
* use class method for radio click handler property
* add custom fast-frame controls for browsers with eyedropper support
Co-authored-by: Chris Holt <chhol@microsoft.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
Adds "Image" as an alias in the linked data control so that the user does not have to type "img".
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This adds an option to the html-render-layer-inline-edit component to commit text changes whenever the text area loses focus and not just when the Enter key is pressed. This feature is also activated by default for the Creator.
There are also a number of bug fixes that were exposed by this change including to the tab navigation in html-render and update messages in the monaco editor in site-utilities.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
closes: #5132
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
To see the change in action start the Creator and add several elements that contain text (like "p"). Double-click the text to edit it. Make a change to the text and do something to cause the textarea to lose focus (click something else, tab out, double-click something else, etc). The change should be committed and reflected in the UI.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change updates the change event to an input event for faster updating in the preview area.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
related to #5138
related to #5136
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Creator and type in the `width` field to see the changes updating the preview automatically.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* force non-volatile binding and update docs to explain that DesignToken does not support volatile bindings
* Change files
Co-authored-by: nicholasrice <nicholasrice@users.noreply.github.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change removes the Fluent UI card example which was not indicative of any current Fluent UI card examples.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Resolves#5135
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Attempt to add the Fluent UI Card, it should no longer add a Fluent UI Card (until #5142 is completed), however the example should no longer exist and in future will add an empty card.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Manual testing only for Creator at present.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
- This will be replaced by templates that are more commonly used for the Fluent UI card in the future
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change adds an `alias` property as an option when scanning JSON schema. This will allow linked data to show additional information in the linked data control and allow aliases to autocomplete text that is typed by a user.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Resolves#5134
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Read through the documentation addition for the README.md and ensure that it makes sense, also build the project and run the Creator to see the changes. You should be able to type "image" to bring up the "img" element.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Unit test added.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change adds an empty example and all JSON schemas belonging to the fluent ui, fast and native element component dictionaries supplied to the Creator. This ensures that any element can be added that belongs to any of those sets of libraries.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Closes#5130
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Attempt to add any previously un-addable element such as "section". An empty element should be created.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
This is currently manual test only as this is a data content issue.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This changes text being used by the libraries and native elements to be consistently tied to a short and long "Lorem ipsum" boilerplate text.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Resolves#5131
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This should change any text inputs that are being added to the updated boilerplate text.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Content changes only.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change fixes an async issue that occurs when FAST components are loaded before the default Fluent UI components in the Creator application. This does not fix the issue where both libraries existing together causes style inconsistencies because of the CSS variable naming overlap. That will be resolved by a future task for name-spacing the CSS variables.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Creator build script to create a production build of the application, then copy to the new `www` folder the `server.js` file in the `@microsoft/site-utilities/statics/server/server.js` and remove lines `22-37` and `49-57`. Also copy the `@microsoft/site-utilities/statics/server/package.json` file. Then run `npm i` and `node server.js`. This should run on `localhost:7001` and should show that the styling async loading issue is resolved when you add a `Card`. The text should no longer be white.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* docs: add an apps and experience section with the first DI article
* docs(dependency-injection): make indentation consistent
* docs(di): content refinement
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
Co-authored-by: Ibrahim Maga <imaga75@hotmail.com>
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This pull request serves a few purposes:
- Adds a list of linked data that cannot be dropped to via schema IDs
- Fixes a drag and drop reordering bug that did not update the active data dictionary ID if the active data dictionary ID was contained in the removed linked data list
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Resolves#5071Resolves#5067
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Build the project and `yarn start` in the Creator site. Attempt to add a few cards, drag and drop them onto various nodes. You should see that the `img` tag which cannot contain content cannot be dropped on. Additionally the run time errors that would occur when the active dictionary id was inside the dragged item should no longer occur.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Unit tests have been added. Additionally a refactor has been done in the `<Navigation />` component to allow for individually unit testing the drag and drop functionality as it is assumed at this time to be impossible to have automated tests in browser.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This makes the CSS layout controlled in the sense that the CSS string value is re-interpreted when it is passed down and applied without allowing a control to dictate it's own value.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Partially solves #5068
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Build the project and run Creator, you should be able to see changes reflected in the CSS layout control when the style attribute on the current element is updated.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Unit tests have been updated.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
- @williamw2 to update the color picker to also be controlled via the value attribute.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change switches the defaults of the design system and design tokens to use the Fluent UI defined schemas and design tokens.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Related to #5069
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
You should now see the Fluent UI default accent color (which was the only difference currently) in the top bar as well as the design tokens tab.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
- Discussions on the effect of having multiple component libraries with their own design tokens, some of which may conflict, to follow.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change adds tooltips for the radio buttons in the FAST tooling CSS layout control.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Closes#5065
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This can be seen either by running the test application in the fast-tooling package or by building the entire project and running the Creator application in the sites folder.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Unit tests added.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change:
- Adds the ability to set a default location for linked data (in the case of web components, this moves a component dropped onto another component to the default slot)
- Increases performance by caching node references during hover
- Ensures that nodes are rendered correcting by testing datasets
- Adding additional data types for more precision on what can be dragged, what can be dropped on, and what are essential non-interactive pieces of data for visual purposes only
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
The most effecting method for testing would be to build the project and run the Creator application, add a Card and attempt to use drag and drop in a variety of ways.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Unit tests have been added for the testable portions of the code. Due to drag and drop functionality being very hard to test this may require a more robust testing plan in the future.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change is an update to the Creator application.
During a component library registration, the fonts are defined in a `<style>` element using the `@font-face`. This adds the `Segoe UI` fonts used in Fluent and the CSS file that adds the FAST font `Aktiv Grotesk`.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This currently does not work as expected as the `--body-font` design token is shared by FAST and Fluent. Therefore `Segoe UI` takes precedence until design tokens are name spaced.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This pull request:
1. fixes an issue where multiple named slots were not appearing, only the first named slot that is accounted for appears
2. fixes an issue where an error was thrown due to the attributes sometimes appearing as arrays
3. fixes an error thrown on the explorer when the `id` from the event used by the `tabs` component is `undefined`.
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
Resolves#5041
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Build and run the component explorer locally, you should be able to see all named slotted items for tabs appear in the tabs component route. You should also be able to add a `<fast-tab>` and a `<fast-tab-panel>` without throwing any errors.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Unit tests have been added.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* docs(fast-frame): correct the style composition example
* docs(fast-frame): update note to also mention template functions
* docs(fast-frame): add link to issue for planned fix
# Pull Request
## 📖 Description
Adding the file component to creator as a StandardControlPlugin for the "src" attribute. This replaces the image src text box in the right side form with a File component button configured to allow image file types (.jpg, .png, .gif). Clicking the button will open a file picker and when an image is selected it is converted to an ObjectUrl which is used for the image src.
*Note: Images added in this way are stored only on the client and only last for the session. No data about the file is transmitted or available outside of the client nor does it utilize cookies in any way.
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change removes the appended "(FAST)" string from the `displayName` in the left `NavigationMenu` component. This is useful for the `Form` to clarify between conflicting names (e.g. "button" native element vs "Button" FAST element) but confusing in the navigation.
Before:
<img width="170" alt="Screen Shot 2021-07-28 at 12 58 02 PM" src="https://user-images.githubusercontent.com/7559015/127396004-205e5332-109e-4dac-97f3-ccc5ba0653b1.png">
After:
<img width="259" alt="Screen Shot 2021-07-28 at 2 06 20 PM" src="https://user-images.githubusercontent.com/7559015/127395963-aa5b65a9-a588-41e4-9a6d-6eec358a7f82.png">
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Component Explorer, you should see the left navigation does not contain "(FAST)" but the form in the right should still contain that appended string.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
- Trigger another site publish for Component Explorer
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
Incoming message, which as of right now have the capability to reset a data dictionary, were not being handled elegantly and would result in unnecessary console logs during runtime. This fixes this issue while more strictly type checking the message.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Creator, see that there are no longer multiple console logs being generated while performing simple actions.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
The consolidated data mapping utility `mapVSCodeHTMLAndDataDictionaryToDataDictionary` in the VS Code utilities was not taking boolean and number values into account and converting the properly. This consolidates the logic for this and the other utility `mapVSCodeParsedHTMLToDataDictionary` that does a direct data map so that they share this logic.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This will fix an issue where typing a boolean attribute, such as `required` on the FAST or Fluent UI Button in the Creator or Component Explorer would cause a validation error as the data was not properly converted to boolean and number values.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Unit tests have been added.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This fixes an issue where if no element library is selected the monaco editor does not recognize the text nodes in the data dictionary.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Disable the `handleLibraryAdded` method executed on line `485` in the `creator.tsx` and then run the Creator application, add a `p` element and see that Monaco Editor editor can interpret the text node used as the `p` example. Try this in the `master` branch and see that Monaco Editor will not add the text inside the `p` element.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* docs: fix various errors discovered while building the site
* docs(sidebars): remove tutorial that needs to be completely re-written
* Change files
Co-authored-by: EisenbergEffect <roeisenb@microsoft.com>
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change adds an appended library name to FAST and Fluent UI components. Below are some screenshots of how this will affect the UI.
Navigation:
<img width="296" alt="Screen Shot 2021-07-23 at 8 40 08 PM" src="https://user-images.githubusercontent.com/7559015/126856365-c0381602-0d62-43ad-866d-8296e6629a69.png">
Form choosing component drop down:
<img width="334" alt="Screen Shot 2021-07-23 at 8 40 27 PM" src="https://user-images.githubusercontent.com/7559015/126856367-9dd87fef-261d-45c5-8931-93c08f125865.png">
Form displaying multiple components from a library:
<img width="316" alt="Screen Shot 2021-07-23 at 8 40 38 PM" src="https://user-images.githubusercontent.com/7559015/126856369-b71597e4-9bca-4b3f-88b7-843e68db5565.png">
Canvas with HTML renderer:
<img width="433" alt="Screen Shot 2021-07-23 at 8 40 48 PM" src="https://user-images.githubusercontent.com/7559015/126856371-be8430c6-c17c-43a6-bb66-423e6005a99b.png">
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Creator and add the different libraries and various components to see the changes.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Site testing is still manual.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* docs: first batch of updates/fixes
* docs(design-systems): updating with provider functions
* docs(fast-element): remove very outdated roadmap
* docs(integrations): update to use new registration system
* docs(accordion): update and expand
* docs(anchor): update and expand
* docs(anchored-region): update and expand
* docs(anchored-region): include in ToC
* docs(avatar): update and expand
* docs(badge): update and expand
* docs(breadcrumb): update and expand
* docs(button): update and expand
* docs(card): update and expand
* docs(checkbox): update and expand
* docs(checkbox): add resources section
* docs(combobox): add, update, and expand
* docs(data-grid): update and expand
* docs(dialog): update and expand
* docs(disclosure): add, update, and expand
* docs(divider): update and expand
* docs(flipper): update and expand
* docs(horizontal-scroll): add initial docs
* docs(listbox): update and expand
* docs(listbox-option): update and expand
* docs(menu): update and expand
* docs(number-field): update and expand
* docs(progress): update and expand
* docs(radio): update and expand
* docs(radio-group): update and expand
* docs(select): update and expand
* docs(skeleton): update and expand
* docs(slider): update and expand
* docs(switch): update and expand
* docs(tabs): update and expand
* docs(text-area): update and expand
* docs(text-field): update and expand
* docs(toolbar): add, update, and expand
* docs(tooltip): update and expand
* docs(tree-view): update and expand
* docs(components): improve additional resources
* Change files
* docs(horizontal-scroll): add missing flipper registration
* docs(skeleton): remove inline css prop set
* Update packages/web-components/fast-foundation/src/tabs/README.md
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
* Update packages/web-components/fast-foundation/docs/integrations/webpack.md
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
* Update sites/website/src/docs/community/writing-documentation.md
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
* Update sites/website/src/docs/design-systems/creating-a-component-library.md
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
* Update sites/website/src/docs/resources/glossary.md
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
* docs(disclosure): use more appropriate content for example
* docs(radios): fixed up radio and radio-group example for aria
* docs(fast-frame): fix indentation
Co-authored-by: EisenbergEffect <roeisenb@microsoft.com>
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
The `onChange` is currently being overwritten for linked data, specifically to allow for the addition of complex examples. This however did not take into account the reordering of linked data, which this PR fixes.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Add a Card to the Creator and in the form, click on the Card to see the internal components, then attempt to drag and drop the components inside it. This should now allow for them to be reordered.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This changes the method to the notification to add a library, not that a library has been added, which will get triggered after.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
See that the Fluent UI components, while added, do not render correctly in the `master` branch. This change fixes this issue by using the correct method which can be seen by adding a Card component.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change enables the Fluent UI component library by default. This is to give designers a faster starting point in their designs by having at least one component library enabled when they begin a project.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Creator, after initialization it should be possible to start typing in the divs default slot and add a Card or other component which should create the Fluent UI component.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Manual testing only for Creator until a test harness is set up.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This fixes a runtime error that was preventing the Component Explorer from loading. Ultimately the schema dictionary was not tied to state and not being passed on via the Editor abstract component, causing a crash from within the Monaco Editor utilities that parse the DataDictionary.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
It is recommended to run both the Creator and Component Explorer to check for any unexpected runtime errors.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* anchored regions uses tranforms
* fix position class not being applied initially
* account for scrolling on document root
* Change files
* update definition
* feedback tweaks
* prettier
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change adds the Fluent UI web component library to Creator. There is a slight issue in Fluent UI which means the build will fail until a publish in Fluent UI fixes the issue. See https://github.com/microsoft/fluentui/issues/18987.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Once this is unblocked by https://github.com/microsoft/fluentui/issues/18987 you will see that two buttons now show up in the left tab, FAST components and Fluent UI components. Both can be added, there are a few caveats however, we are using the Design Tokens from FAST for editing in the right pane. This means that when adding Fluent UI components, the accent color is available but will not affect any components. Additionally, if both component libraries are added, there may be some discrepancies between packages. There is also an issue where both libraries have components that are named the same. This will need to be resolved by prefixing or affixing the library name. See next steps for a future resolution.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
- Allow libraries to add an additional pane to the right rail for configuration, this will be used for the Design Tokens for FAST and Fluent UI component libraries but should be open ended enough to allow for any extra library configuration to take place
- Prefix or affix the library name to the component name in the Form and Navigation
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This fixes an issue where an image example was being used instead of a paragraph in Creator.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This can be tested by adding a paragraph by typing in "p" in the Form when running Creator.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* Partial port of docs
* adding 'creating a component library' section
* add design-token section
* removing todo links
* fixing up links
* docs(creating-a-component-library): address basic community feedback
* docs(creating-a-component-library): clarify some details and improve
* docs(creating-a-component-library): working a bit more on flow/clarity
* docs(vnext): fix a few minor typos based on review feedback
* docs(design-system-overview): expanding and refining the content
* doc(fast-frame): working on flow improvements
* docs(fast-frame): work on clarity, examples, and flow
* docs(design-tokens): review and format
* Updated design token examples and descriptions
* adding css example
Co-authored-by: nicholasrice <nicholasrice@users.noreply.github.com>
Co-authored-by: Rob Eisenberg <rob.eisenberg@microsoft.com>
Co-authored-by: Brian Heston <47367562+bheston@users.noreply.github.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change updates the export for `@alpha` web components and services from the `@microsoft/fast-tooling` package so they can be imported from the root location. It also corrects a few mis-typed const names that should be lowercase and it normalizes some file structures for easier exporting.
This change affects the Creator site and Explorer site as the pathing has been updated to reflect that these services and web components can now be imported from the root of the package.
Due to issues resulting from exporting web components from the root, jest test have been updated with mock files and the `jest-environment-jsdom-sixteen` package has been added to allow for more modern global methods assumed to be available in browsers.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
It should not be necessary to run the sites as the build gate should break if the pathing is incorrect.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
Per the next steps bulleted item in #4932 the schemas of a component library are now only added to the dictionary once the library has been added. This prevents the addition of components before they have been loaded into the preview area.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Creator locally, attempt to add the "Card" component in the `div` default slot, see that it doesn't show up. Then add the component library in the left pane libraries tab, try to add "Card" again and it should display in the dropdown.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
Adding preview mode toggle to creator. When creator is set to preview mode the left and right columns and the code view are hidden and the viewer container style is changed to accurately reflect the rendering markup. In addition the HTMLRender navigation and inline edit functionality is suppressed so that the user can interact with rendered markup.
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This PR adds logic where adding the FAST components library prompts the preview application to dynamically load and register components from the library. Without this action the components have not been included and will not render.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Creator application and try to add a Card, this should not render correctly as the components have not been imported and registered. Then add the FAST components library using the button in the Libraries tab, the Card should render correctly. Additionally you can add the library first then the card, this should result in the correct rendering of the Card.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
- Make the components unavailable to be added until the library they are comprised of are added
- Add in the Fluent UI component library using the same methods the FAST library inclusion is employing
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
As part of the work to enable dynamic imports, this change splits the shell of the site and the preview into two applications that communicate through the iframe. This will allow separate logic for the preview such as adding the library scripts and requesting them to be dynamically imported from the shell UI.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
The app should work exactly the same, this can be tested in FAST Creator using `yarn start`.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This adds the initial component adding UI to FAST Creator, with the FAST components selected as they are not being dynamically imported yet.
Before:
<img width="258" alt="Screen Shot 2021-06-29 at 3 49 25 PM" src="https://user-images.githubusercontent.com/7559015/123877209-9f85dc00-d8f1-11eb-9dff-4c17b785c7ed.png">
After:
<img width="255" alt="Screen Shot 2021-06-29 at 3 49 09 PM" src="https://user-images.githubusercontent.com/7559015/123877197-9c8aeb80-d8f1-11eb-8bd9-1b8a18674bf6.png">
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
To test, start up the FAST Creator with `yarn start` and see the change in the left pane.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Currently there is no test plan until a test harness has been added for the application.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This pull request changes the data structure that the Creator app expects for component libraries per #4883. It also moves the examples to the example files.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This change should not actually change any functionality and adding web components or native elements in the Creator should function as it currently is.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Tests are pending an integrated site testing solution.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change adds the FAST avatar `<fast-avatar>` component to the Component Explorer site.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Run the Component Explorer site in `sites/fast-component-explorer` with `yarn start`. Navigate to the Avatar using the menu on the left, you should be able to see the`<fast-avatar>` render.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [x] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [x] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This updates the Creator app by removing the `<fast-design-system-provider>` component as a wrapper and uses the design tokens when updates occur.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This change does not update the theme, @bheston do you have a reference as to what needs to happen for theme switching between light and dark mode to occur?
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This updates the Component Explorer app by removing the `<fast-design-system-provider>` component as a wrapper and uses the design tokens when updates occur.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This change does not update the theme, @bheston do you have a reference as to what needs to happen for theme switching between light and dark mode to occur?
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This updates the FAST Tooling examples site by removing the `<fast-design-system-provider>` component as a wrapper and uses the design token to change the theme.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Simply run `yarn start` in the fast-tooling-examples site.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
* export design tokens and color recipe DI symbols
* fix imports in other packages
Co-authored-by: nicholasrice <nicholasrice@users.noreply.github.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change updates the `@microsoft/fast-tooling` package experimental web components to the new APIs from `@microsoft/fast-foundation`. This change affects `<color-picker>`, `<html-render>`, and `<html-render-layer-navigation>`.
Since all affected code is experimental, this is not marked as a version bump.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
All sites and manual testing apps appear to be taking the changes. Please double check this by running `yarn start` in the `fast-tooling` (navigating to the `render` section), `fast-tooling-react` (navigating to the `controlPluginWithCSSOverrides` dropdown value), and `fast-creator` in the sites folder.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
The tests have been updated with the new fixture updates which were previously copied over, they have been moved to the `__test__` folder.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change updates to use the new Design System registry as well as named imports from `@microsoft/fast-components` as well as updates the dependencies to not be on `latest` but the current version. This change will be mirrored in another PR to master so that vNext can be unblocked and master can be subsequently unblocked.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This change appears to run fine on the manual apps and web components that are registered to the design system are showing up. Let me know if there is a better method, we are making the assumption that either the user is not going to be on a separate version of the Design System and will be using the same class with this change.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
* support foundation element on accordion and accordion item
* update anchor to use foundation element
* update AnchoredRegion to extend FoundationElement
* update Badge to extend FoundationElement
* update breadcrumb and breadcrumb item to extend FoundationElement
* update Button to extend FoundationElement
* update checkbox to extend from FoundationElement
* update Dialog to extend FoundationElement
* update disclosure to extend FoundationElement
* update divider to extend FoundationElement
* update Flipper to extend FoundationElement
* update horizontal scroll to extend FoundationElement
* update Listbox and ListboxOption to extend FoundationElement
* update combobox to extend FoundationElement
* update select to extend combobox and update tests
* fix listbox option styles and export
* update tests (wip)
* update Menu and MenuItem to extend FoundationElement
* update number field to extend FoundationElement
* update base name values
* fix: prevent the mixin helper from copying over constructor properties
* feat: fixture ergonomic improvements for foundation elements
* test: fix Anchor and associated unit tests based on new system
* remove incorrect tagFor usage
* update radio and radiogroup
* update skeleton
* update slider and slider label
* update switch
* update tabs et all to use FoundationElement
* update text area and text field to use foundation el
* Update tooltip to use FoundationElement
* update tests and tree item and view
* remove website from lerna packages in favor of npm registry to prevent breaking changes for the time being
* update progress and progress ring to use Foundation element
* fixing the tests
* feat: enable fixtures to handle N foundation elements and custom system
* fixing tests!
* Change files
* fix errors in fast-website
* update typings for explorer
* update naming convention to lowercase fast
* update imports for sites
* Change files
* update template names to lowercase
* update style casing and apply updates to component registries
* update tsdoc links for templates
Co-authored-by: Rob Eisenberg <rob.eisenberg@microsoft.com>
* exit with an error if no paths given to copy script
* consolidate and normalize scripts in website package
* update docusaurus from 2.0.0-alpha.70 to 2.0.0-beta.1
* fix badge url in fast-components doc
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change updates the spec file with details on how adding a component library will work in the Creator app.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Read through the change and note any part that does not make sense. Keep in mind the messaging between `creator.tsx` and `preview.tsx` is because the preview exists in an iframe.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [ ] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
Adding a new layer to the HTMLRender component that allows for inline editing of text and adding this functionality to Creator. Expected behavior is whenever text within the preview area is double clicked a textarea is placed in the same position of the text node allowing for user input. The text area will resize based on the input and pressing the Enter key will commit the changes. Pressing Esc, Tab or clicking outside of the text area will cancel the interaction.
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
Planned work for the Creator includes making libraries of components dynamic imports. To facilitate this the libraries have been split which will make them easier to work with as a potential dynamic import in the future. This change also adds a spec file for the Creator site to allow the speccing out of features that the site will have.
Related to #4845
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This change only re-organizes some exports and does not affect the current implementation of the data examples. To check this, run `yarn start` in the FAST creator site folder and add components that have examples using the Form.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change prevents tree shaking out the layout web component from `@microsoft/fast-tooling` when the Creator site is built for production.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Build and run the site in production mode to see this working.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This creates a CSS layout web component in `@microsoft/fast-tooling` that can be used by itself or with the experimental custom css control in `@microsoft/fast-tooling-react`. It primarily uses the CSS flexbox to update CSS either by the change event or an `onChange` property assigned to the element.
This PR also contains the integration into the Creator design tool.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Running the Creator site will show off the control in the right pane, to view it by itself run `yarn start` to use the manual testing app in `@microsoft/fast-tooling` package.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
New unit tests have been added for this component.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This is a documentation only update and adds some clarification on the message system (still incomplete), a brief overview of what is contained within the Creator site and some additional code comments on some typescript interfaces.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Though this is incomplete, it should provide some clarifying notes around the message system and how the Creator is intended to work on a baseline level.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [ ] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
* update tabbable
* add key constants
* add toolbar component to fast-foundation
* add toolbar component to fast-components
* set fast-combobox to delegate focus
* add toolbar component definition
* allow other keypresses to pass through radio components
* allow foundation toolbar to handle foundation radio group interactions
Co-authored-by: Chris Holt <chhol@microsoft.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This pull request removes the `@microsoft/fast-tooling` as a dependency in the `@microsoft/fast-components` package. This is done by instead of using the custom format and TypeScript definition, we instead use and validate against the VS Code definition directly.
This solves an issue where Beachball fails publishing due to not strictly testing against package versions as well as brings us closer to enabling intellisense in the Monaco Editor.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This change affects the `@microsoft/fast-components` package and the Component Explorer site. It has been tested and the definitions are showing up in the Component Explorer site but it would be good to get a few more pairs of eyes on it.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
A new test using the Ajv validator is used to validate the component definitions against the VS Code custom data definition.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change updates the list of allowed-to-edit CSS properties in the Creator and updates the generated file imported.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Reviewers can see the change by running `yarn start` in the `fast-creator` site folder and looking in the right pane of the site.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
Place `no-paint`, `use-defaults` and `direction` to the advanced category in the Creator site.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
This simplifies the design system form view in the Creator and can be viewed by going to the fast-creator site and running `yarn start`.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change ensures that rendered content for `<style>` elements are not wrapped in an additional `<span>` element.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
You can test this by running `yarn start` in the `fast-creator` site folder.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This adds the alpha CSS custom control to the Creator site, with a subset of CSS properties.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
For manual testing, run `yarn` at the root level to update with the changes from `site-utilities` then in the `fast-creator` site use `yarn start`. You should be able to see the CSS control in action in the `<Form />` component in the right panel.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Pull Request
## 📖 Description
Moving native HTML definitions from sites/site-utilities to packages/tooling/fast-tooling to make them more accessible to other components. Needed for the new html-render component in order to prevent circular dependencies.
After this is completed tests need to be added for html-native.definition.ts. See #4608
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
### 🎫 Issues
<!---
* List and link relevant issues here.
-->
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This pull request adds the experimental color picker web component to the Creator site.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
# Description
<!--- Describe your changes. -->
Adds the slider to the Create site design system editing pane.
Before:
After:
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
This should make the controls more user friendly.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [x] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
This change adds a list of the JSON schemas to the CDN folder via the schema generation script.
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
This will allow anyone to get the list of JSON schemas and their locations and schema `$id` for use.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
The CSS properties subset was not included in the `dist` folder as `allowJs` was omitted from the `tsconfig.json`.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
When running `yarn build` in the `sites/site-utilities` directory, there should now exist the css-data.js file in the `dist` directory.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
Co-authored-by: Chris Holt <chhol@microsoft.com>
Co-authored-by: Ibrahim Maga <imaga75@hotmail.com>
# Description
<!--- Describe your changes. -->
This change adds categories to the design system tab of the Creator.
Before:
After:
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
This should initially hide some of the more advanced options in the FAST design system provider as well as provide additional context to other attributes.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
* refactor(fast-element)!: rename Directive, disambiguate types, and reorganize (#4414)
* refactor(fast-element): rename Directive and other types to disambiguate
* refactor(fast-element): reorganize internals
* fix: data-grid stores generated templates (#4412)
* store generated templates
* similar for row and cell item templates
* chore: update background color on menu item (#4416)
* update input background to change color on selected
* removed accent beackground color on menu-item
* fixed HC color on submenu
* docs(tools): add hot module reload documentation
Co-authored-by: Stephane Comeau <scomea@microsoft.com>
Co-authored-by: Kham Udom <37851220+khamudom@users.noreply.github.com>
Co-authored-by: Aaron Wentzel <16669785+awentzel@users.noreply.github.com>
* works
* auto update
* doc stuff
* remove auto mode
* updateThreshold
* return of auto
* spec
* revert change to update handler
* add release tag
* update schema
# Description
<!--- Describe your changes. -->
This adds all current component JSON schemas to the statics/assets folder to deploy them to the CDN for easy access.
This is a one time change until an update structure for keeping schemas synced with component updates can be determined.
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
JSON schemas for the components may need to be referenced from time to time from outside sources for validation.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
Adds the conversion of scenarios before webpack build is started (this should not be needed but it appears there is some potential async issue going on when webpack is running the build)
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
Fixes#4495
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [x] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
Co-authored-by: Aaron Wentzel <16669785+awentzel@users.noreply.github.com>
# Description
<!--- Describe your changes. -->
This change adds a message event listener to catch and attempt to parse and apply a data dictionary.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [x] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
* feat: use two form instances and multiple message systems for the design system and components
* Add design system
* Test fixes
* PR Fixes
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
# Description
Removing all dependencies from Creator and Explorer to JSS, the old design system and the FAST react MSFT package and replacing them with FAST web components.
## Motivation & context
This PR merges the following PRs into master:
https://github.com/microsoft/fast/pull/4374https://github.com/microsoft/fast/pull/4400https://github.com/microsoft/fast/pull/4419https://github.com/microsoft/fast/pull/4453https://github.com/microsoft/fast/pull/4456
These include the following issues:
#4262#4264#4266#4267#4269#4271#4272#4274#4275
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
Co-authored-by: Mathieu Lavoie <44816587+m4thieulavoie@users.noreply.github.com>
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
# Description
<!--- Describe your changes. -->
The two data types, `DataDictionary` which the `fast-tooling` package uses, and a `string[]` value that the Monaco Editor uses, are currently kept in sync using the `onDidChangeContent` callback for Monaco Editor and `postMessage` to the `MessageSystem`.
This creates an issue where any setting of the value of the Monaco editor causes the `onDidChangeContent` to be called which we cannot control. To mitigate this issue, an additional check in the `MonacoAdapter` service uses the string value last set by the Monaco Editor, and if the change does not affect it this means that the update came from `fast-tooling` and that the Monaco editor need not fire a `postMessage` to update the `DataDictionary`.
This work is currently still being evaluated as the `MonacoAdapter` has still not been released publicly and is subject to change as the features mature.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
This PR is a merging of the feature branch containing the following PRs:
- https://github.com/microsoft/fast/pull/4322
- https://github.com/microsoft/fast/pull/4387
- https://github.com/microsoft/fast/pull/4397
- https://github.com/microsoft/fast/pull/4403
- https://github.com/microsoft/fast/pull/4430
- https://github.com/microsoft/fast/pull/4434
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
Resolves#2530Resolves#2575
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [x] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
Co-authored-by: Chris Holt <chhol@microsoft.com>
# Description
<!--- Describe your changes. -->
Adds the `types` prop to the `<Navigation />` component implementation in the Creator site. This results in direct nesting of nodes and removal of all other data types (such as string, null, number etc which complicates the navigation).
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
This change adds a build script to convert only specific CSS properties for use in the sites so that a subset of CSS can be edited via the Creator or Component Explorer.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
This maps the native HTML definitions to JSON schema using the new structure.
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
Incorrect titles in the native HTML element definitions were being mapped.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [x] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
Co-authored-by: Aaron Wentzel <16669785+awentzel@users.noreply.github.com>
* add playwright harness script and configs (#4229)
* split harness and server
* add environment variables
* fix tsconfig conflicts
* add README
* update yarn.lock after rebase
* install playwright latest
* Replace rollup-plugin-copy with copyfiles
* cross-env environment var setting
* add playwright CI
* add ci-workflow to linux machine
* add playwright ci to linux environment
* work flow fixes in linux
* resolve conflict issue
* playwright worflow
* playwright workflow
* fix run workflow
* install playwright for servers
* change tittle for the build
* Update .github/workflows/ci-weekly.yml
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
* Update build/copy.js
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
* remove blank lines
* renaming test dir to __test__
* organize gitignore files
* Update packages/web-components/fast-components/__test__/README.md
* fix environment variable casing
* remove abbreviation from environment variable
* sort package.json scripts
Co-authored-by: John Kreitlow <863023+radium-v@users.noreply.github.com>
Co-authored-by: John Kreitlow <john.kreitlow@microsoft.com>
Co-authored-by: nicholasrice <nicholasrice@users.noreply.github.com>
Co-authored-by: Ibrahim Maga <imaga75@hotmail.com>
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
* fixing incorrect link addresses
* align development script with the rest of the package
Co-authored-by: nicholasrice <nicholasrice@users.noreply.github.com>
# Description
An issue occurs during the first load of the explorer site which causes the height of the iframe to be incorrect. This fix addresses it by using the same logic the resize functionality uses to calculate the height.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
* update to programmatically deploy robots based on environment
* update to cleanup duplicate and erroroneous files
* remove space before 2nd line command for user agent
* update to edit conditions for robots.txt
# Description
<!--- Describe your changes. -->
Replaces the deprecated React badge with the `<fast-badge>` from the `@microsoft/fast-components` package.
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
Resolves#4266
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
This adds the number field config to the Component Explorer. When navigating to the number field route it will no longer throw an error.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [x] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [x] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
Updates the class name of the dev tools tab panel to be inline with previous class names, updates the padding to include the desktop screen sizes.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [x] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
This change updates the `dist` folder to have separate folders for `esm` and `cjs` module resolutions.
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
This allows `cjs` to be used in a node environment for various utilities such as the MDN data converter. This particular use case can facilitate smaller package bundles by allowing the CSS configuration footprint to be as small as possible as the conversion can be shipped without re-converting during application run time.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [x] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
<!--- Describe your changes. -->
This change replaces the deprecated `<Pivot />` react component with the `@microsoft/fast-components` `<fast-tabs>`.
<img width="779" alt="Screenshot 2021-01-21 174347" src="https://user-images.githubusercontent.com/7559015/105434360-4615d480-5c10-11eb-918f-59aeb55ddc3f.png">
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
This not only updates to use the new web components but resolves the contrast issue on high contrast white.
I can only speculate what it was about `<Pivot />` that caused this issue, but since all other variables remained the same during testing and we needed to update these components anyway, that's where the investigation ended.
Resolves#3980
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [x] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
# Description
Cross Platform Validation
<!--- Describe your changes. -->
Changed made to
1. modified prettier:diff to prettier check and write in the package.json file
added run prepare workspace.
2. ON windows we have added this script to resolve the line ending
run: |
git config --global core.autocrlf false
git config --global core.eol lf
we have also specify the shell script as bash cmd in the workflow so the string can be treated as in Linux
shel: bash
3. dangerouslySetInnerHTML={{ __html: FooterTemplate }} get replaced by
dangerouslySetInnerHTML={{ __html: FooterTemplate() }} to resolve a units test that was failing.
changed made in sites/fast-color-explorer/app/site-footer.tsx
## Motivation & context
<!--- What problem does this change solve? -->
This fix os validation on windows and mac
closes#4058
<!--- Provide a link if you are addressing an open issue. -->
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [x] **Bug**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
Co-authored-by: Ibrahimmaga <ibrahim.maga@yahoo.fr>
Co-authored-by: John Kreitlow <john.kreitlow@microsoft.com>
Co-authored-by: John Kreitlow <863023+radium-v@users.noreply.github.com>
* Adding fast-number-field component
* adding documentation
* Add slots do definition and updating to kebab casing
* Using DelegatesARIATextBox
* Adding inputmode for mobile devices
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
Co-authored-by: Chris Holt <chhol@microsoft.com>
# Description
fix a typo on the names of the images and fixed the path for accent.png.
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [ ] **Chore**: A change that does not impact distributed packages.
- [x] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/community/contributor-guide
-->
* add high contrast document to website
* add images to assets directory and add more information and images to document
* update heading, fixing typos.
* addressing comments to add notes and more references from MDN
* update url link for images
* addressed comments on grammar suggestions
* add note regarding forced-colors-adjust and addressed more grammar comments
* adding the word, of, to the notes
* fixed punctuation on reason for forcedColorsStylesheetBehavior
* addressed hidden comments from John
* working
* working
* working
* working
* working
* working
* working
* working
* working
* working
* new template mechanism
* working
* cell binding works v1
* cell config
* cell binding values update
* working
* working
* working
* start on focus mgmt
* update spec
* row keyboarding works
* base keyboarding works
* add focus targeting in cells
* basic header rendering
* fix keyboarding
* rough styling
* update spec
* update styling
* move header to light DOM
* header cell focus
* add header cell template example
* updating cell templates
* collapse to a single slot for all rows, update column data and index on child rows
* improved story
* rework column width mechanism, add column resize example.
* collapse rows into one class pt.1
* headers are just rows
* collapse to one cell class
* fix column template switching
* adding/removing rows
* improve story example
* start on modifying values
* grid column handling for cells
* rename DataGridColumn to ColumnDefinition
* update spec
* minor fixes
* fixed old cells not being removed
* add/update definition files
* stub in test files
* stub in config and scenarios for site
* fix column initialization
* base sticky header support
* update spec, scroll into view
* remove list box example, fix rename bug
* add some tests
* add cell tests
* add row tests
* add data grid tests
* tweak spec
* high contrast
* add switch row templates to examples
* cell item template improvements
* update spec
* not yellow
* move item generation templates to main template files so they can be set there
* add read me and scenario example
* cleanup and respond to feedback
* respond to feedback
* add page up/down behavior
* fix warnings
* remove draft spec
* move spec
* remove unnecessary part names on slots.
* use template children instead of query to track rows and cells
* refocus row on data change
* use event name references
* update read me
* add template generators
* update api report
Microsoft FAST Builds
Ibrahim Maga
Piyush Goyani
Aaron Wentzel
Jane Chu
Stephane Comeau
Chris Holt
John Kreitlow
William Wagner
Nicholas Rice
Rob Eisenberg
Brian Heston
Christian Nunciato
nicholasrice
Dexter Lesaca
Brook Durant
Roman
Hardik Pithva
Rob Barber
Kham Udom
