EDCD / EDCD/EDMarketConnector

Class based plugins API

Open
#1,227 9 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
1.3k
Forks
182
Avg merge
1m
Merged PRs (30d)
1

Description

**Describe the enhancement**

Currently plugins work by developers providing module level functions with particular names, this is simple but can make it difficult when we want to alter the plugin API

My personal preference is for plugins to implement a base class that we provide. That should also make it easier for us to do things like the "per plugin logging" and others. It can also give us more control over how we present functions that have to run on the main loop or can run in a thread.

I've raised this as a placeholder for discussion.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by reviewing the existing module-level plugin API and the discussion about a base class, per-plugin logging, and main-loop versus threaded functions. Done would require an agreed class-based plugin API and an implementation plan.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.