MerginMaps / MerginMaps/python-api-client
Create unified api interface for api integration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 23
- Forks
- 12
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
The idea: all api call will be separated in module called api , api_v2, where we will define functions jut for api calls.
mc.api.push_start()
mc.api_v2.push_project_version()
etc.
Originally posted by @MarcelGeo in https://github.com/MerginMaps/python-api-client/pull/262#discussion_r2318204284
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.
Research direction
Start by reviewing the existing API call modules and the public entry points implied by mc.api.push_start() and mc.api_v2.push_project_version(). Define the intended boundary between api and api_v2 before changing code; done means API calls are consistently exposed through the unified interface described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100