* Define matchers to test promise fulfillment
These are useful for validating that promises depend on other events prior to fulfilling.
* Expose custom matchers to jest projects
Team-specific projects are not touched here to try and reduce review burden.
* Block browser local operations awaiting reseed
This should closes a narrow race condition resulting from storage operations during a reseed event.
* Import from barrel file
This might fix the failing test, but I'm not sure _why_
* Document helper methods
* Validate as few properties as possible per test
* Simplify expected value representation
* Allow waiting in promise matchers
* Specify resolution times in promise orchestration tests.
* Test behavior triggering multiple reseeds.
* Fix typo
* Avoid testing implementation details
* Clear reseed on startup
in case a previous process was aborted in the middle of a reseed.
* Correct formatting
* Create tracker that can await until expected observables are received.
* Test dates are almost equal
* Remove unused class method
* Allow for updating active account in accout service fake
* Correct observable tracker behavior
Clarify documentation
* Transition config service to state provider
Updates the config fetching behavior to be lazy and ensure that any emitted value has been updated if older than a configurable value (statically compiled).
If desired, config fetching can be ensured fresh through an async.
* Update calls to config service in DI and bootstrapping
* Migrate account server configs
* Fix global config fetching
* Test migration rollback
* Adhere to implementation naming convention
* Adhere to abstract class naming convention
* Complete config abstraction rename
* Remove unnecessary cli config service
* Fix builds
* Validate observable does not complete
* Use token service to determine authed or unauthed config pull
* Remove superfluous factory config
* Name describe blocks after the thing they test
* Remove implementation documentation
Unfortunately the experience when linking to external documentation is quite poor. Instead of following the link and retrieving docs, you get a link that can be clicked to take you out of context to the docs. No link _does_ retrieve docs, but lacks indication in the implementation that documentation exists at all.
On the balance, removing the link is the better experience.
* Fix storybook
* Change everything to Uint8Array
related to https://github.com/jestjs/jest/issues/14379
* Work on failing type tests
* Revert changes to custom matcher setup
* Remove last BufferArrays from tests
* Fix custom matcher type errors in vscode
* Remove errant `.buffer` calls on Uint8Arrays
* Encryption Pair should serialize Array Buffer and Uint8Array
* Fix EncArrayBuffer encryption
---------
Co-authored-by: Thomas Rittson <trittson@bitwarden.com>
