* Use typescript-strict-plugin to iteratively turn on strict
* Add strict testing to pipeline
Can be executed locally through either `npm run test:types` for full type checking including spec files, or `npx tsc-strict` for only tsconfig.json included files.
* turn on strict for scripts directory
* Use plugin for all tsconfigs in monorepo
vscode is capable of executing tsc with plugins, but uses the most relevant tsconfig to do so. If the plugin is not a part of that config, it is skipped and developers get no feedback of strict compile time issues. These updates remedy that at the cost of slightly more complex removal of the plugin when the time comes.
* remove plugin from configs that extend one that already has it
* Update workspace settings to honor strict plugin
* Apply strict-plugin to native message test runner
* Update vscode workspace to use root tsc version
* `./node_modules/.bin/update-strict-comments` 🤖
This is a one-time operation. All future files should adhere to strict type checking.
* Add fixme to `ts-strict-ignore` comments
* `update-strict-comments` 🤖
repeated for new merge files
* setup popover component template and basic story
* add a11y features
* add multiple positions for the popover
* add stories for open right and left
* prevent panel from hugging edges of screen
* fix typo
* add popover arrow depending on position
* add buttons to stories
* add figma preview
* move toward directive approach
* add all positions
* add header input
* add close functionality
* make standalone component
* add a11y import
* add all stories
* add story controls/args
* add module of standalone components
* gracefully handle text wrap and align close button to top for longer headings
* update semantic html
* add story for open state
* use bitIconButton
* adjust styles
* add public close method
* setup walkthrough mode
* add walkthrough mode
* revert to before walkthrough service added
* add triggerRef to stories
* change property name
* add Escape key to close events
* add initially open state
* add docs
* minor reformatting
---------
Co-authored-by: William Martin <contact@willmartian.com>
