* generate forwarded alias with SL and AD
* added forwarded email to type list
* add ApiService dep
* ApiServiceAbstraction
* use proper status codes
* only generate on button press
* reset username to `-`
* reset username when forwarded
* Authorization header for anonaddy
* use proper anonaddy json path
* firefox relay support
* update description for firefox
* log username generation errors
* Switch to jest
* Fix jslib-angular package name
* Make angular test project
* Split up tests by jslib project
* Remove obsolete node test script
* Use legacy deps with jest-preset-angular
* Move web tests to common
* Remove build from pipeline
This was only being used because we were not using ts runners.
We are now, so build is unnecessary
* add ellipsis pipe
* run prettier
* Account for ellipsis length in returned string
* Fix complete words case
* Fix another complete words issue
* fix for if there are not spaces in long value
* extract length check to beginning of method
* condense if statements
* remove log
* Remove error Response type check
Minimization is impacting type checking in a non-consistent way.
The previous type check works locally,
but not from build artifacts 🤷. We only set `captchaRequired` on
our errors when we want a resubmit with captcha included, so we're safe
keying off that
* linter
Collapsed groupings have regressed to not maintaining their state through restarting clients.
The state mangement refactor erroniously began saving this field to memory instead of disk, but there were some other issues that changing this brought on that are also fixed in this commit.
Changes:
1. Save collapsedGroupings persistantly in StateService
2. Adjust the type of collapsedGroupings on the Account model from a Set<string> to a string[]
* This is the way we were storing this value in previous releases, and saving the entire set object breaks.
3. Adjust the StateService getter/setter for collapsedGroupings to expect a string[]
4. Extract a string[] from the GroupingsComponent groupings that is a Set<string> before saving
* [bug] Fix logout timeout action for inactive accounts
* Pass userId in to the logout callback parameter to the vaultTimeoutService. The message handle in desktop already expects this.
* Set lastActive on account login, and null it on account deauthentication. This prevents an issue where newly logged in accounts immediatly time out due to inactivity.
* Add userId to locked callbacks
* Add userId to log out callback
* Use different strategy classes for different types of login
* General refactor and cleanup of auth logic
* Create subclasses for different types of login credentials
* Create subclasses for different types of tokenRequests
* Create TwoFactorService, move code out of authService
* refactor base CLI commands to use new interface
Some clients have unique global setting defaults (and unique global settings)
For example: the web vault defaults to light theme, but most clients with theme support default to system theme.
The current way we handle GlobalState is buried in jslib and not easily extendible in clients.
To fix this, we need to treat GlobalState as a generic in the StateService and StateMigration service and allow for its extension in those methods and anywhere GlobalState is inited.
Jake Fink
Oscar Hinton
Anthony Garera
Thomas Rittson
Federico Maccaroni
Kyle Spearrin
Robyn MacCallum
Matt Gibson
Vincent Salucci
Melanie Kanavakatini
Addison Beck
Jake Howard
Addison Beck