- description: |
Share code in parsers of committee commands. This doesn't share the CLI's behavior.
# uncomment types applicable to the change:
type:
# - feature # introduces a new feature
# - breaking # the API has changed in a breaking way
# - compatible # the API has changed but is non-breaking
# - optimisation # measurable performance improvements
- refactoring # QoL changes
# - bugfix # fixes a defect
# - test # fixes/modifies tests
# - maintenance # not directly related to the code
# - release # related to a new release preparation
# - documentation # change in code docs, haddocks...
Context
While doing PRs recently in this part of the codebase, I realized that some places had code duplicated, without a good reason. Sharing will also fixes to affect multiple commands at once in the future, and also helps keeping different commands consistent.
Changelog
Context
More sharing is possible (e.g. hot VS cold), but I don't want to stack too much in one PR.
How to trust this PR
Checklist