Describe the problem
Hey, I am dealing with a deadlock situation where two participants join at nearly the same time. It would be useful, especially in my case, to have legal access to "joinedAtMs" from participantInfo. Is there any reason not to expose this field like joinedAt is?
I'd happy to open a PR. I just want to confirm if there is any reason not to use this field.
Thank you!
Describe the proposed solution
Implement a getter for the participantInfo's joinedAtMs inside the Participant class.
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response
Describe the problem
Hey, I am dealing with a deadlock situation where two participants join at nearly the same time. It would be useful, especially in my case, to have legal access to "joinedAtMs" from
participantInfo. Is there any reason not to expose this field likejoinedAtis?I'd happy to open a PR. I just want to confirm if there is any reason not to use this field.
Thank you!
Describe the proposed solution
Implement a getter for the
participantInfo'sjoinedAtMsinside the Participant class.Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response