v1/conversations/list/v2 The V1 API returnes the data structure with new access_role logical
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 334
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 50
Description
Describe the bug
v1/conversations/list/v2 API in 2023-10-23 (Chart Release 4.39.0) release。returnes the data structure with new access_role logical.
"access": [
"invite",
"code"
],
"access_role": [
"team_member",
"non_team_member",
"guest",
"service"
]
so the iOS APP cannot correctly process the data returned by the v1/conversations/list/v2 API.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
V1 API maintains the original logic
"access": [
"invite",
"code"
],
"access_role": "non_activated",
"access_role_v2": [
"team_member",
"non_team_member",
"guest",
"service"
],
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the v1/conversations/list/v2 handler and its response schema. Compare the current access_role and access_role_v2 fields with the expected response in the issue; done means the V1 endpoint preserves access_role as a single value while exposing the newer role list separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 34/100