Ouput from CLI frontend seems to drop structure
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Reproduce the issue with ghapi orgs.list_members --org fastai and inspect the CLI output path that formats the returned users. Confirm that each user is emitted as a separate map in an array rather than one flattened list, then verify the command produces the expected nested structure.
Written by the indexing model from the issue text.
Description
If I do ghapi orgs.list_members --org fastai from the command line, the output I get is
[- login: hamelsmu
- id: 1483922
- node_id: MDQ6VXNlcjE0ODM5MjI=
- avatar_url: https://avatars.githubusercontent.com/u/1483922?v=4
- gravatar_id:
- url: https://api.github.com/users/hamelsmu
- html_url: https://github.com/hamelsmu
- followers_url: https://api.github.com/users/hamelsmu/followers
- following_url: https://api.github.com/users/hamelsmu/following{/other_user}
- gists_url: https://api.github.com/users/hamelsmu/gists{/gist_id}
- starred_url: https://api.github.com/users/hamelsmu/starred{/owner}{/repo}
- subscriptions_url: https://api.github.com/users/hamelsmu/subscriptions
- organizations_url: https://api.github.com/users/hamelsmu/orgs
- repos_url: https://api.github.com/users/hamelsmu/repos
- events_url: https://api.github.com/users/hamelsmu/events{/privacy}
- received_events_url: https://api.github.com/users/hamelsmu/received_events
- type: User
- site_admin: True, - login: jph00
- id: 346999
- node_id: MDQ6VXNlcjM0Njk5OQ==
- avatar_url: https://avatars.githubusercontent.com/u/346999?v=4
- gravatar_id:
- url: https://api.github.com/users/jph00
- html_url: https://github.com/jph00
- followers_url: https://api.github.com/users/jph00/followers
- following_url: https://api.github.com/users/jph00/following{/other_user}
- gists_url: https://api.github.com/users/jph00/gists{/gist_id}
- starred_url: https://api.github.com/users/jph00/starred{/owner}{/repo}
- subscriptions_url: https://api.github.com/users/jph00/subscriptions
- organizations_url: https://api.github.com/users/jph00/orgs
- repos_url: https://api.github.com/users/jph00/repos
- events_url: https://api.github.com/users/jph00/events{/privacy}
- received_events_url: https://api.github.com/users/jph00/received_events
- type: User
- site_admin: False, - login: racheltho
- id: 2602738
- node_id: MDQ6VXNlcjI2MDI3Mzg=
- avatar_url: https://avatars.githubusercontent.com/u/2602738?v=4
- gravatar_id:
- url: https://api.github.com/users/racheltho
- html_url: https://github.com/racheltho
- followers_url: https://api.github.com/users/racheltho/followers
- following_url: https://api.github.com/users/racheltho/following{/other_user}
- gists_url: https://api.github.com/users/racheltho/gists{/gist_id}
- starred_url: https://api.github.com/users/racheltho/starred{/owner}{/repo}
- subscriptions_url: https://api.github.com/users/racheltho/subscriptions
- organizations_url: https://api.github.com/users/racheltho/orgs
- repos_url: https://api.github.com/users/racheltho/repos
- events_url: https://api.github.com/users/racheltho/events{/privacy}
- received_events_url: https://api.github.com/users/racheltho/received_events
- type: User
- site_admin: False]
As you can see, the data for all users in mangled into a single flat list. I assume this is not correct, as we should get something like an array of maps where each user is a separate entry.
- Dominant language
- Python
- Stars
- 687
- Forks
- 69
- Avg merge
- 1m
- Merged PRs (30d)
- 2
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 AnswerDotAI/ghapi
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
AnswerDotAI/ghapi#158 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AnswerDotAI/ghapi#120 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
AnswerDotAI/ghapi#208 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
AnswerDotAI/ghapi#201 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
AnswerDotAI/ghapi#186 ·
All issues in AnswerDotAI/ghapi
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100