* update eslint-config-rules and versions, fix fast-element lint errors
* fix fast-router lint issues
* fix foundation errors
* fix figma plugin lint errors
* fix react issues and disable ban types for empty object as its useful in tsx defs
* Change files
* temporary allow major version for eslint package
add js file override to eslint config (#5310)
* add js file override to eslint config
* deduplicate lockfile
* remove no-non-null-assertation and add noImplicitAny and strictPropertyInitialization to base tsconfig
* fix new errors in web utils
* turn off noImplicitAny and strictPropertyInitialization for fast-element due to errors
* turn off strictPropertyAssignment and noImplicitAny for fast-foundation tsconfig
* resolve certain no-non-null-assertion errors and disable others
* turn off noImplicitAny and strictPropertyInitialization for fast-components
* disable anchored region and palette
* resolve color constants, dsp, dialog issues
* turn off strictPropertyInitialization and noImplicitAny for fast-router
* turn off no-non-null-assertion in eslint
* turn off strictNullChecks, strictPropertyInitialization, and noImplicitAny in fast-colors
* update fast-react-wrapper
* Change files
* fixup web utilities dom typings
* fixup fast-web-utilities html spec files
* disable strict null checks due to numbers, rtl, and string test and fn issues
* fixup final react wrapper issues
* add types specifically for the test package
* fix figma plugin type issues
* ignore non-null errors for color in fast-color-explorer
* fix type error by casting due to implicit any
* 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
* add beachball changes to test pipeline failures
* remove unneeded set-origin
* added service token
* update to rule out github service issue as break
* update names for git auth
* update arg for git name email
* update to comment out testing while testing
* update package config
* update beachball package and move to prod dep
* update npm pat
* update to proper dep add statement
* update to solve gh pat
* add default registry -r
* config npmrc
* add npmrc
* resole revert
* token
* cmt token
* env variable
* un-comment install dependencies and testing
* update yarn.lock with beachball
* Merges to "users/awentzel/update beachball v1" - some fixes to make the workflow work (#4476)
* fixing up the beachball publish job
* reduced the script slightly to re-use global env ideally
* adding check and change gate
* check for change file with no run
* remove check for change, it should be added to the daily build since it trigger the PR
* fix environment typo
* add --no-publish
* testing for non trigger file changes
* test beachball
* Change files
* Token validation
* add to ci-daily Check for the presence of changed files inside ./change
* change type to none
* update spelling
* change trigger on schedule only
* fix indentation
* remove added listbox for testing
* add pre-release tag
* fix cron; set to midnight trigger
* add tag canary
* remove tag
Co-authored-by: Aaron Wentzel <16669785+awentzel@users.noreply.github.com>
Co-authored-by: Kenneth Chau <34725+kenotron@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>
# Description
This merges CLI work for managing the Azure infrastructure. These scripts perform operations for creating new services, destroying old services, and updating existing services. This is beta and mostly usable with some features yet to be implemented which are documented in comments and with GH issues.
This begins a FAST CLI extending the Azure CLI simplified maintainability with consistency, speed, and reliability.
<!--- Describe your changes. -->
## Motivation & context
To provide an equal ability for all collaborators to perform common service needs. For example, perform release deployments of websites.
<!--- 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: -->
- [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.
- [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: Jane Chu <7559015+janechu@users.noreply.github.com>
* chore: remove xss for compliance as it gives false sense of security
* update to replace all http to https for security improvements
* Update build/testing/sauce-labs/test-browsers.js
Co-authored-by: John Kreitlow <863023+radium-v@users.noreply.github.com>
* Update packages/web-components/README.md
Co-authored-by: John Kreitlow <863023+radium-v@users.noreply.github.com>
* Update README.md
Co-authored-by: John Kreitlow <863023+radium-v@users.noreply.github.com>
* Update packages/web-components/fast-components/README.md
Co-authored-by: John Kreitlow <863023+radium-v@users.noreply.github.com>
Co-authored-by: John Kreitlow <863023+radium-v@users.noreply.github.com>
# Description
Reduce complexity for CSS tagged template compression. Also spotted some invalid commas in the `progress` stylesheets.
## Motivation & context
The CSS tagged template minifier was combining `:host() .child` selectors, causing styles to not get rendered properly.
## 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/en/contributing/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/en/contributing/working
-->
* chore: change all instances of fast-dna to fast
* chore: revert cloudinary url changes
* chore: revert medium blog url change
* docs: fix some broken links in the intro
* add writing style to documentation
* add testing documentation
* add policy to documentation
* add standards to documentation
* update to migrate sauce labs to internal only in build/testing
* initial move of files into new sub directories
* modify pathing for tsconfig, package.json references
* move website to sites folder
* update build steps for website
* ensure old docusaurus files stay ignored
* move jss-utils to react and figma plugin to tooling
* test conversion to yarn
* test updated yaml for circleci
* fixing builds
* update circleci to install via yarn docs
* setup prettier as global install for test
* use sudo to install lerna
* update typings for tooling package plugin controls
* fix component explorer issues
* doc updates
* fix angular tests with tsconfig
* test cache and frozen lockfile
* ensure workspaces are built
* change build to prepare
* fixing tests
* update component explore readme conversion path for node modules
* setup tests to stream again
* update working documentation
* update lockfile
* change back to npm from yarn install
* update readmes to reflect npm vs yarn
* revert tooling changes
* restored .json files
* updated pathing in app to be more specific
* add convert script
* refined convert script and deleted json files
* if tmp folder does not exsist create it
* refactor: update how copy readme script prints output to terminal to make it easier to read
* update glob function so that it doesn't ignore lowercase readme titles
* update variable names to make them read more like a counter
* update broken links after migrated msft-docs to explore
* update to include generated file
* Revert "update to include generated file"
This reverts commit 81e142bc5407909ee9bf05e103b57e336d60ed63.
* dir structure created
* add typescript package
* delete unused file
* remove doctype packages
* update per Jason feedback
* update to fix lint errors in markdown
* remove package as it will be deprecated in future
* update to remove util from packages
* adds test component with no documentation, adds default documentation message when no documentation is provided
* updates based on comments
* updates logic and removes div wrapper
* adds back in readme data
* fixes extra spacing
* fixes spaces
* adds test to ensure all components are exported
* moves function to helper folder, simplifies tests
* removes ignoreCodes, WARN will show during unit-tests
* test prettier
* fixes messaging
* adds tests at root
* Finishes tests for export function
* simplifies logic using requires
* removes comment
* updates based on comments
* fixes formatting
* removes unneeded packages
* removes unneeded package data
* removes react related config
* removes npmignore
* updates based on comment
* updates package
* removes prettier
* removes unneeded package data
* adds missing export :)
Aaron Wentzel
Chris Holt
John Kreitlow
Ibrahim Maga
Nicholas Rice
gpresland
Rob Eisenberg
Jane Chu
Jeff Smith
Nicholas Rice
Julia McGeoghan
Stephane Comeau
Nicolas LoGiudice