Output product enhancements
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Following on work from #10, a few more tasks that might be valuable:
- Homogenizing the configuration structure between plugin-provided output products and built-in output products, e.g. moving all built-in products from using their bespoke configuration keys to a similar structure used by the plugins (within e.g.
product.builtin.<name> - Enforcing & handling output product filenames from within common code, instead of leaving it open to plugin implementations (which e.g. could write to incorrect locations/filenames with unparseable versions, etc.)
- More elegantly handling the addition/removal of output product plugins w/ the Run History File contents and logic
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 by reviewing the work from issue #10 and tracing the configuration for plugin-provided and built-in output products. Then inspect the common output-product filename handling and Run History File logic to define the scope; done means these three areas have an agreed, consistent design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100