[PM-29956] Add logging to sponsorship redemption flow

[connerbw]

🎟️ Tracking

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

📔 Objective

Add client-side console logging to the Families for Enterprise sponsorship redemption flow to capture diagnostic information when users encounter errors.

Changes:

• families-for-enterprise-setup.component.ts — logs via LogService (browser console) at each step: token presence/length, pre-validation result, organization creation success, redeem start, redeem success, and on failure the full ErrorResponse including statusCode, message, and validationErrors

All logs are prefixed with [Sponsorship] for easy filtering in DevTools. No PII is logged — only internal IDs, enum values, status codes, and server-provided error messages.

This is the client-side companion to the server-side logging PR. Together they cover model state validation failures (client captures the response) and business logic failures (server logs the specific gate that rejected the request).

[connerbw]

Companion PR: bitwarden/server#7381

[github-actions]

Bitwarden Claude Code Review

Overall Assessment: APPROVE

This PR adds client-side console logging to the Families for Enterprise sponsorship redemption flow in families-for-enterprise-setup.component.ts. The changes inject LogService and add structured log statements at key decision points: token presence checks, pre-validation results, redeem start/success/failure, and organization creation callbacks. All logs use a consistent [Sponsorship] prefix for filtering.

No security, correctness, or breaking change issues were identified. No sensitive data (tokens, PII) is logged -- only internal IDs, enum values, status codes, and server-provided error messages. The removal of the no-unused-vars eslint-disable on the catch variable is a correct cleanup since e is now referenced in the error logging block.

Code Review Details

No findings to report. The changes are well-scoped diagnostic logging with appropriate log levels and no risk of data exposure.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 15 lines in your changes missing coverage. Please review.
✅ Project coverage is 46.92%. Comparing base (f7475d8) to head (8c9da12).
⚠️ Report is 4 commits behind head on main.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...orships/families-for-enterprise-setup.component.ts	0.00%	15 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #19947      +/-   ##
==========================================
- Coverage   46.92%   46.92%   -0.01%     
==========================================
  Files        3909     3909              
  Lines      118268   118283      +15     
  Branches    18093    18096       +3     
==========================================
- Hits        55502    55501       -1     
- Misses      58593    58609      +16     
  Partials     4173     4173              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Checkmarx One – Scan Summary & Details – 84bb2304-f5a8-432e-8b29-e12db8882c08

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

[JaredScar]

Looks good for Admin-Console changes, thanks! Merge conflicts will need fixing though, feel free to DM me on Slack when need a re-review!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud