Should we create custom errors instead of relying on the base error class?

[fuxingloh]

It's out of the scope of this PR, but should we create custom errors instead of relying on the base error class? Something like

class MnemonicValidationError extends Error {
    message = "mnemonic sentence checksum invalid"
}

so we can use it in later error handling with something like:

try {
 // ... do something ...
}catch(err){
    if(err instanceof MnemonicValidationError){
        //  handle it somehow
    }
}

expect(() => {
        MnemonicHdNodeProvider.fromWords(words, regTestBip32Options, false)
      }).not.toThrow(MnemonicValidationError)

This is probably something that needs discussion from the team and is more of a change in convention than something related to this PR.

Originally posted by @cwkang1998 in #1225 (comment)

/kind feature
/area packages

[defichain-bot]

@fuxingloh: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository.

[fuxingloh]

Btw this is very low priority