Skip to content

feat: expose sub_account_name on Number resource#312

Merged
avinashp-plivo merged 2 commits into
masterfrom
FNT-370
May 26, 2026
Merged

feat: expose sub_account_name on Number resource#312
avinashp-plivo merged 2 commits into
masterfrom
FNT-370

Conversation

@avinashp-plivo
Copy link
Copy Markdown
Contributor

Summary

  • Adds explicit test coverage that Number.sub_account and Number.sub_account_name are surfaced by the SDK on rented number get/list APIs.
  • The fields already flow through at runtime via PlivoResource's dynamic attribute mapping (self.__dict__.update(response)); this release makes the behavior part of the contract.
  • Bumped version 4.60.1 → 4.60.2.

Mirrors the parallel FNT-370 work in plivo-go#244, plivo-ruby#264, plivo-java#317, plivo-php#371, plivo-dotnet#312.

Test plan

  • python3 -m unittest tests.resources.test_numbers passes locally (9/9)
  • Updated numberGetResponse.json / numberListResponse.json fixtures include sub_account_name

🤖 Generated with Claude Code

Sub-account name is forwarded automatically via dynamic attribute on
PlivoResource (response keys -> instance attrs). This commit adds:
- explicit test coverage asserting number.sub_account and
  number.sub_account_name are set from the mock response
- version bump to 4.60.2 and CHANGELOG entry

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@avinashp-plivo avinashp-plivo merged commit 524c115 into master May 26, 2026
7 of 12 checks passed
@avinashp-plivo avinashp-plivo deleted the FNT-370 branch May 26, 2026 05:59
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.

2 participants