Refactor project specific loading functions.
Open
Nobody has claimed this yet.
project plugins
- Dominant language
- Python
- Stars
- 8
- Forks
- 7
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 23
Description
This seems like it should be straightforward to write a generic loading function here rather than project specific.
https://github.com/MetOffice/CDDS/blob/ac9ae76006c11f050072a94a920352e248b47334/cdds/cdds/common/plugins/plugin_loader.py#L44-L51
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with cdds/cdds/common/plugins/plugin_loader.py at lines 44-51 and inspect how the project-specific loading functions are used. Determine the shared behavior they can expose through a generic loading function, then verify that the existing plugin-loading paths still work without project-specific implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100