* fix(register): [PM-27085] Account Register Uses New Data Types - Initial changes. * test(register): [PM-27085] Account Register Uses New Data Types - Fixed tests. * test(register): [PM-27085] Account Register Uses New Data Types - Updated tests. * feat(register): [PM-27085] Account Register Uses New Data Types - Added feature flag. * fix(register): [PM-27085] Account Register Uses New Data Types - Removed unnecessary part of the payload. * fix(register): [PM-27085] Account Register Uses New Data Types - Changed the feature flag to be gated with the other password input changes. * fix(register): [PM-27085] Account Register Uses New Data Types - Added protection for feature flagged state. * fix(register): [PM-27085] Account Register Uses New Data Types - Removed unnecessary comment. * fix(register): [PM-27085] Account Register Uses New Data Types - Addressed feedback. * fix(register): [PM-27085] Account Register Uses New Data Types - Fixed tests and added comment. * fix(register): [PM-27085] Account Register Uses New Data Types - Fixed another test. * fix(register): [PM-27085] Account Register Uses New Data Types - And last test fix. * fix(register): [PM-27085] Account Register Uses New Data Types - Removed unneeded code. * fix(register): [PM-27085] Account Register Uses New Data Types - Updated comments and fixed code from feedback. * fix(register): [PM-27085] Account Register Uses New Data Types - Updated comments again with small styling fix. * fix(register): [PM-27085] Account Register Uses New Data Types - Switched to snapshot testing and explicit checks for unlock and authentication data for feature flag on. Also addressed pr comments. * test(register): [PM-27085] Account Register Uses New Data Types - Made explicit checks for critical pieces of data in tests. * fix(feature-flag): [PM-27085] Account Register Uses New Data Types - Added in feedback from comments. Default registration tests have snapshots now and web registration has more dry code. |
||
|---|---|---|
| .checkmarx | ||
| .claude | ||
| .codescene | ||
| .github | ||
| .husky | ||
| .storybook | ||
| .vscode | ||
| apps | ||
| bitwarden_license | ||
| docs | ||
| libs | ||
| scripts | ||
| .browserslistrc | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc.json | ||
| angular.json | ||
| babel.config.json | ||
| clients.code-workspace | ||
| CONTRIBUTING.md | ||
| eslint.config.mjs | ||
| jest.config.js | ||
| jest.preset.js | ||
| LICENSE_BITWARDEN.txt | ||
| LICENSE_GPL.txt | ||
| LICENSE.txt | ||
| lint-staged.config.mjs | ||
| nx.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| tailwind.config.js | ||
| tsconfig.base.json | ||
| tsconfig.eslint.json | ||
| tsconfig.json | ||
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.