IdentitySet class does not have 'phone' property
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Start at the IdentitySet model entry point and reproduce the IdentitySet(phone=Identity(...)) construction from the issue. Compare the supported constructor parameters with the REST API shape and verify that a phone target can be represented in the generated request body without using additional_data.
Written by the indexing model from the issue text.
Description
Describe the bug
When trying to make a phone call, I specify the IdentitySet of the Target user like this:
targets = [
InvitationParticipantInfo(
identity = IdentitySet(
phone = Identity(
id = "+mynumber"
)
)
)
]
However I get the following error "IdentitySet.init() got an unexpected keyword argument 'phone'" stating that this parameter is not available for the IdentitySet class.
This works when calling from the rest API
Expected behavior
Parameter should be present in the class, just like the user parameter for calling an teams userid
How to reproduce
target_identity = IdentitySet(phone=Identity(id=graph_p.phone_number))
target = InvitationParticipantInfo(
identity = target_identity
)
request_body = Call(
callback_uri = "myballback",
tenant_id = tenant_id,
source = ParticipantInfo(
identity = IdentitySet(
application = Identity(
id = bot_instance_id
)
)
),
targets = [target],
requested_modalities = [Modality.Audio],
media_config = ServiceHostedMediaConfig(
pre_fetch_media = []
)
)
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
Use IdentitySet additional_data parameter in order to inject the phone parameter to the body
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_
- Dominant language
- Python
- Stars
- 630
- Forks
- 96
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-sdk-python
-
status:waiting-for-triage type:bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
microsoftgraph/msgraph-sdk-python#1570 ·
-
status:waiting-for-triage type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoftgraph/msgraph-sdk-python#1563 ·
-
Needs: Attention :wave: type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoftgraph/msgraph-sdk-python#1287 · 2 comments · 1 reaction ·
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
microsoftgraph/msgraph-sdk-python#1578 ·
-
status:waiting-for-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoftgraph/msgraph-sdk-python#1557 ·
All issues in microsoftgraph/msgraph-sdk-python
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·