Stabilize plugin creation API

Open
#27 2 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, data

Research direction

No files or tests are named. Start by locating the existing plugin creation API and the rows import/export paths, then compare how plugins currently provide import and export behavior. Done means the plugin contract is clearly defined so rows handles lazy importing and plugins only provide the required data generators.

Written by the indexing model from the issue text.

Description

docs help wanted plugin

Create a better API for writing plugins, taking into consideration that the library will try to do the most it can so the only plugin's job will be to import/export data (rows will automatically deal with importing data in a lazy way or not, for example -- the plugin should only provide a generator on the import function).

Dominant language
Python
Stars
886
Forks
137
No merged PRs in 30d

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 turicas/rows

All issues in turicas/rows

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.