Skip to content

feat: add number_of_employees field to Profile API#320

Draft
Jai Shankar (jaishankar-plivo) wants to merge 1 commit into
masterfrom
feat/add-number-of-employees-to-profile
Draft

feat: add number_of_employees field to Profile API#320
Jai Shankar (jaishankar-plivo) wants to merge 1 commit into
masterfrom
feat/add-number-of-employees-to-profile

Conversation

@jaishankar-plivo

Copy link
Copy Markdown

Summary

Adds a new optional number_of_employees field to the Profile (10DLC/A2P account profile) create & update APIs, mirroring the corresponding campaign-service backend change.

Implemented in exactly the same places and style as the recently added doing_business_as (DBA) field:

  • ProfileAdder — field + constructor param + accessor (creator overload added in Profile.java)
  • ProfileUpdater — field + builder method + getter
  • ProfileResponse — field + getter
  • ProfileTest — create/get/update coverage
  • profileGetResponse.json fixture

Details

  • Public/JSON field name: number_of_employees (Java numberOfEmployees, serialized via the existing snake_case naming policy — no explicit annotation, matching DBA).
  • Type: optional String, no client-side enum validation (server validates).
  • Allowed values documented in comments (not enforced): BETWEEN_1_AND_10, BETWEEN_11_AND_50, BETWEEN_51_AND_200, BETWEEN_201_AND_500, BETWEEN_501_AND_2000, BETWEEN_2001_AND_10000, MORE_THAN_10001.
  • Version bumped 5.48.1 → 5.48.2 (pom.xml, version.txt) and CHANGELOG entry added, matching the DBA release pattern.

🤖 Generated with Claude Code

Mirrors the campaign-service backend change adding number_of_employees as
an optional string to the Profile create & update requests. Added in the
same places and style as the recently added doing_business_as (DBA) field:
field, builder/creator method, response getter, tests, and fixture. No
client-side enum validation; allowed values are documented in comments and
validated server-side.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant