90b7197279
* feat: scaffold new badge service structure * feat: add state override * feat: add priority-based override * feat: implement state clearing * feat: add docs to badge service functions * feat: add support for setting icon * feat: implement unsetting * feat: implement setting text * feat: add support for setting background * fix: default icon * feat: clean up old update-badge * feat: save state using StateProvider * feat: migrate auth status badge updating * feat: migrate autofill badge updating * fix: auto set to default values * chore: woops, clean up copy-pasta * fix: lint and types * chore: nit updates from PR review * feat: remove ability to send in arbitrary icons * feat: move init to separate function * fix: wrong import * fix: typing issues * fix: try again to fix typing issues * feat: scaffold tests for new tabId-specific states * feat: add diffence util function * feat: add support for limiting state to tabId * feat: re-implement autofill badge updater to only update when a tab actually changes * feat[wip]: always set all tabs when changing the general state * feat[wip]: implement general states for mutliple open tabs * feat[wip]: implement fully working multi-tab functionality * feat: optimize api calls * feat: adjust storage * chore: clean up old code * chore: remove unused log service * chore: minor tweaks * fix: types * fix: race condition causing wrong icon on startup The service assumes that the first emission from the state will be an empty one and discards it (techincally it just doesn't act on it because pairwise requires a minimum two emissions). This caused issues when a service is able to update the state before the observable got a change to properly initialize. To fix this we simply force an empty emission before anything else, that way we will always react to the emission from the state provider (because that would end up being the second emission). We then use distinctUntilChanged to avoid unecessarily acting on an empty state.
Bitwarden Client Applications
This repository houses all Bitwarden client applications except the mobile applications (iOS | android).
Please refer to the Clients section of the Contributing Documentation for build instructions, recommended tooling, code style tips, and lots of other great information to get you started.
Related projects:
- bitwarden/server: The core infrastructure backend (API, database, Docker, etc).
- bitwarden/ios: Bitwarden iOS Password Manager & Authenticator apps.
- bitwarden/android: Bitwarden Android Password Manager & Authenticator apps.
- bitwarden/directory-connector: A tool for syncing a directory (AD, LDAP, Azure, G Suite, Okta) to an organization.
We're Hiring!
Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden.
Contribute
Code contributions are welcome! Please commit any pull requests against the main branch. Learn more about how to contribute by reading the Contributing Guidelines. Check out the Contributing Documentation for how to get started with your first contribution.
Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file.