NRLMMD-GEOIPS / NRLMMD-GEOIPS/pluginify

Expose commonly used components at the top level and give obvious names

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

Nobody has claimed this yet.

Dominant language
Python
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Requested Update

Description

Imports from pluginify are a little messy right now. We should figure out what components need to be imported by other packages frequently and expose them in a more usable way. For example, GeoIPS currently uses the following imports, each of which could be simplified if pluginify were to expose them.

from pluginify.plugin_registry import PluginRegistry
from pluginify.commandline_typer import configure_logging
Background and Motivation
  • [ OPTIONAL: Provide additional detailed information and background related to this issue ]
Alternative Solutions
  • [ OPTIONAL: If appropriate, list alternative fixes that could be considered]
Environment
  • [ IF APPROPRIATE: Corresponding repository versions ]
Code to demonstrate issue
  • [ IF APPROPRIATE: Can include steps here to identify/demonstrate bug fix or desired feature ]
Checklist for Completion
  • <!--- Include a list of steps that must be complete in order to close this Issue --->

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.

Research direction

Start by reviewing pluginify.plugin_registry and pluginify.commandline_typer, especially PluginRegistry and configure_logging, then inspect how other packages import commonly used components. Define the top-level import paths and clearer names, and verify that the GeoIPS examples can use the simplified imports without breaking existing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
developer-experience
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.