Skip to content

Conversation

@nikwithak
Copy link
Contributor

๐ŸŽŸ๏ธ Tracking

https://bitwarden.atlassian.net/browse/PM-25012

๐Ÿ“” Objective

This PR adds the data field to the Cipher struct, and adds a function for parsing that field into the appropriate CipherType (Identity, SshKey, Login, SecureNote, Card) on the client-side, rather than consuming the server-provided values.

The function sits unused - after #455 is merged, we should consider adding this to the CiphersClient::get and CipherClient::list functions behind a new feature flag.

โฐ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation
    team

๐Ÿฆฎ Reviewer guidelines

  • ๐Ÿ‘ (:+1:) or similar for great changes
  • ๐Ÿ“ (:memo:) or โ„น๏ธ (:information_source:) for notes or general info
  • โ“ (:question:) for questions
  • ๐Ÿค” (:thinking:) or ๐Ÿ’ญ (:thought_balloon:) for more open inquiry that's not quite a confirmed
    issue and could potentially benefit from discussion
  • ๐ŸŽจ (:art:) for suggestions / improvements
  • โŒ (:x:) or โš ๏ธ (:warning:) for more significant problems or concerns needing attention
  • ๐ŸŒฑ (:seedling:) or โ™ป๏ธ (:recycle:) for future improvements or indications of technical debt
  • โ› (:pick:) for minor or nitpick changes

@claude
Copy link

claude bot commented Oct 17, 2025

Claude encountered an error โ€”โ€” View job


I'll analyze this and get back to you.

@nikwithak nikwithak marked this pull request as ready for review October 17, 2025 20:29
@nikwithak nikwithak requested review from a team as code owners October 17, 2025 20:29
@github-actions
Copy link
Contributor

github-actions bot commented Oct 17, 2025

Logo
Checkmarx One โ€“ Scan Summary & Details โ€“ f05c7793-b79a-49c2-be9b-3af9fcb96f0d

Great job! No new security vulnerabilities introduced in this pull request

@codecov
Copy link

codecov bot commented Oct 17, 2025

Codecov Report

โŒ Patch coverage is 97.92208% with 8 lines in your changes missing coverage. Please review.
โœ… Project coverage is 78.96%. Comparing base (8ef7951) to head (0288979).
โš ๏ธ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
crates/bitwarden-vault/src/error.rs 0.00% 7 Missing โš ๏ธ
crates/bitwarden-vault/src/cipher/cipher.rs 99.73% 1 Missing โš ๏ธ
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #517      +/-   ##
==========================================
+ Coverage   78.70%   78.96%   +0.26%     
==========================================
  Files         296      296              
  Lines       30500    30884     +384     
==========================================
+ Hits        24005    24388     +383     
- Misses       6495     6496       +1     

โ˜” View full report in Codecov by Sentry.
๐Ÿ“ข Have feedback on the report? Share it here.

๐Ÿš€ New features to boost your workflow:
  • โ„๏ธ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • ๐Ÿ“ฆ JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@gbubemismith gbubemismith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks really good. I just have a few questions

@gbubemismith
Copy link
Contributor

@nikwithak I think we can target main directly

@nikwithak nikwithak requested a review from a team as a code owner October 22, 2025 21:45
@nikwithak nikwithak requested a review from coroiu October 22, 2025 21:45
@nikwithak nikwithak changed the base branch from vault/feature/cipher-versioning to main October 22, 2025 21:45
@sonarqubecloud
Copy link

Copy link
Contributor

@coroiu coroiu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think platform owns any of this code anymore, but I'll approve anyways :)

@nikwithak nikwithak merged commit 21432b5 into main Oct 31, 2025
52 of 53 checks passed
@nikwithak nikwithak deleted the vault/PM-25012/cipher_opaque_data branch October 31, 2025 21:37
bw-ghapp bot pushed a commit to bitwarden/sdk-swift that referenced this pull request Oct 31, 2025
โ€ฆta field to Cipher type, and add functions for client-side parsing of the field. (bitwarden/sdk-internal#517)
@rishancmm-eng
Copy link

Tracking
https://bitwarden.atlassian.net/browse/PM-258

๐Ÿ“” Objective

This PR adds the data field to the Cipher struct, and adds a function for parsing that field into the appropriate CipherType (Identity, SshKey, Login, SecureNote, Card) on the client-side, rather than consuming the server-provided values.

The function sits unused - after #455 is merged, we should consider adding this to the CiphersClient::get and CipherClient::list functions behind a new feature flag.

Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation
    team

๐Ÿฆฎ Reviewer guidelines

  • ๐Ÿ‘ (:+1:) or similar for great changed
  • ๐Ÿ“ (:memo:) or โ„น๏ธ (:information_source:) for notes or general info
  • โ“ (:question:) for questions
  • ๐Ÿค” (:thinking:) or ๐Ÿ’ญ (:thought_balloon:) for more open inquiry that's not quite a confirmed
    issue and could potentially benefit from discussion
  • ๐ŸŽจ (:art:) for suggestions / improvements
  • โŒ (:x:) or โš ๏ธ (:warning:) for more significant problems or concerns needing attention
  • ๐ŸŒฑ (:seedling:) or โ™ป๏ธ (:recycle:) for future improvements or indications of technical debt
  • โ› (:pick:) for minor or nitpick changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants