consider decoupling repository discovery from plugin discovery

Open
#10 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
search

Research direction

Start by tracing the current GitHub code search, known-repositories input, and plugin discovery flow; no files or tests are named in the issue. First establish a concrete benefit for separating the phases, then define completion as repository-search output and known repositories being passed into an independent plugin-discovery phase.

Written by the indexing model from the issue text.

Description

move the GitHub code search into its own step, then take the output of that (and known-repositories) as input to a plugin discovery phase.

but only do this if there's a concrete benefit. right now, it would just be code churn.

Dominant language
Python
Stars
40
Forks
19
Avg merge
8h 20m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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 HexRaysSA/plugin-repository

All issues in HexRaysSA/plugin-repository

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.