Make interface of toxin module same as iedb

Open
#12 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
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by locating the toxin and iedb modules and comparing their public entry points. Clarify the intended interface and compatibility requirements before making changes; done means the toxin module exposes the same agreed interface as iedb.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
Python
Stars
58
Forks
16
Avg merge
2d 12h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 openvax/pepdata

All issues in openvax/pepdata

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.