* Add support for replaying from har file
* Fix merge
* Improvements
* Add export and folder support
* Minor tidy ups
* Fix lint
* Add doc
* Update doc with correct fallback HTTP status code
* Fix typo
* Remove merge to master on PR tests due coverage issue
* Update GI action versions from 2 to 3
* Re-enable HTMl coverage for tests
* Remove deprecated nyc in package configuration from merge conflict; Ignore further folders from coverage
* Change tests checkout and print changed files on test during coverage job
* Add codecov configuration
* Add coverage if instrumented
* Remove changed files steps
* Increase memory for unit test
* Add .vue extension to unit test instrumentation
Add .vue extension to unit test instrumentation
* Remove HTML coverage due 'file:' issue
* Remove HTML report and add .vue files
* Restore GHA fetch to 1 for last commit
- white page errors should not be visible in prod
- these were were enabled in all envs via the port of shell/initialize/client.js after nuxt
- that came from the output of a template
- the template has some features on via debug state when built
- we now disable these features in prod
- Additionally..
- set some process values that were being skipped but still used
- always log uncaught errors in `fetch`s. in theory we should be monitoring $fetchState.error but we never do. this has led to some painful debugging with customers
- caused by EXCLUDE_OPERATOR_PKG defaulting to truthy
- which meant no plugins were loaded by the ui
- which meant button to reload ui given changes to plugins was always shown
- when meant extension e2e test that removed plugin immediately used it to reload without waiting for remove to finish
- Fixes#8979
- Remove clash of `test: /\.md$/,` entries
- The removed entry might be a copy and paste error. Going back to pre-nuxt removeal the `url-loader` was associated with loading images
- https://github.com/rancher/dashboard/blob/v2.7.2/shell/nuxt.config.js#L492
- i'm not sure if we don't need the custom loader now, images do seem to work
- build time env var was not passed through to where it was used in runtime
- resulted in RC builds looking for resources in `/` instead of `/dashboard`
The release version of rancher appears to expect the favicon at the root directory. Dev expected it to be under the public directory. I changed dev to use the root directory as well
https://github.com/rancher/dashboard/issues/8794
Neil MacDougall
Alexandre Alves
Evgeniya Vashkevich
Richard Cox
Giuseppe Leo
Richard Cox
richa
Richard Cox
codyrancher
Cody Jackson
Nancy