github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-05 23:38:51 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[PR #5724] [MERGED] Support both camel and pascal case for AccountKeysJson #12141

New Issue
Closed
opened 2026-04-11 03:35:33 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-11 03:35:33 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/5724
Author: @SaintPatrck
Created: 8/18/2025
Status: ✅ Merged
Merged: 8/18/2025
Merged by: @SaintPatrck

Base: main ← Head: fix-account-keys-model-casing

📝 Commits (1)

  • eab75a0 Support both camel and pascal case for AccountKeysJson

📊 Changes

1 file changed (+23 additions, -10 deletions)

View changed files

📝 network/src/main/kotlin/com/bitwarden/network/model/AccountKeysJson.kt (+23 -10)

📄 Description

🎟️ Tracking

Internal change

📔 Objective

The AccountKeysJson and its nested classes now support both camelCase and PascalCase for their JSON properties by using @JsonNames annotation. This ensures compatibility with different API response formats.

This change is necessary because the GetToken response uses PascalCase while the SyncResponseJson models use camelCase.

⏰ 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

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/5724 **Author:** [@SaintPatrck](https://github.com/SaintPatrck) **Created:** 8/18/2025 **Status:** ✅ Merged **Merged:** 8/18/2025 **Merged by:** [@SaintPatrck](https://github.com/SaintPatrck) **Base:** `main` ← **Head:** `fix-account-keys-model-casing` --- ### 📝 Commits (1) - [`eab75a0`](https://github.com/bitwarden/android/commit/eab75a00c9636718012bbab9e1d00566886376a8) Support both camel and pascal case for AccountKeysJson ### 📊 Changes **1 file changed** (+23 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `network/src/main/kotlin/com/bitwarden/network/model/AccountKeysJson.kt` (+23 -10) </details> ### 📄 Description ## 🎟️ Tracking Internal change ## 📔 Objective The `AccountKeysJson` and its nested classes now support both camelCase and PascalCase for their JSON properties by using `@JsonNames` annotation. This ensures compatibility with different API response formats. This change is necessary because the `GetToken` response uses `PascalCase` while the `SyncResponseJson` models use `camelCase`. ## ⏰ 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 <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+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 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-11 03:35:33 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#12141
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?