Create unified api interface for api integration

Open
#270 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

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.

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

Dominant language
Python
Stars
23
Forks
12
Avg merge
2d 13h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/python-api-client

All issues in MerginMaps/python-api-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.