Merge LegacyClientCmdError
into CmdError
#195
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog
Context
Proposes to merge the
LegacyClientCmdError
type intoCmdError
.This will make it easier to share code between legacy and era-based. An example of this is
GovernanceCmdError
which is the same error type used by era-based and legacy code.For example the legacy
run
function for a particular legacy command can delegate to the correspondingrun
function for the corresponding era-based command without having to convert between different error type hierarchies.Note, we already share
GovernanceCmdError
between the two hierarchies. This change formalises this by making it so at the top level as well and avoids us accidentally creating two error-type hierarchies going forward.Checklist
See Running tests for more details
.cabal
files are updatedhlint
. See.github/workflows/check-hlint.yml
to get thehlint
versionstylish-haskell
. See.github/workflows/stylish-haskell.yml
to get thestylish-haskell
versionghc-8.10.7
andghc-9.2.7