additional information for `sign` when returning false

[reez]

Describe the enhancement
I'm wondering if anyone has potentially thought of any alternatives to the return type than what currently exists for sign Result<bool, SignerError>

Use case
I'm specifically thinking about a client app signing a transaction and getting bool of false back without additional information of why sign returned false.

Maybe they were expecting it to return false but maybe not; that client app may expect successful signing, not receive true or SignerError back, but get back false instead without extra context, on what could be considered an imporant operation for their app.

Additional context
Just looking for feedback/thoughts if there has been conversation about this historically/presently, and any possible thoughts.

[A-y-ush]

Hey, so from what I understand . The problem we are trying to solve is explaining why the transaction has not been signed (completely) which means the signing is done but the PSBT is not finalised yet. If I am understanding it right, it does make sense to add the potential reasons for this. Although I am also unaware about any prior discussion on this.
we can create separate cases for which the PSBT is not finalised during the transaction and return those.

[A-y-ush]

@reez can I get assigned to this issue? I would like to work on it.

[reez]

@A-y-ush I don't seem to have access on this specific repo to assign this to anyone, I think this is a good item for me to mention on this weeks Lib Dev Team Call to check in on other folks thoughts on how they'd like to proceed as well as get it assigned to you, thanks for the feedback and volunteering to take this on!

[reez]

@A-y-ush you've been assigned now, this is a good research topic, and may not make it into the final beta release or anything, but would love to see what you come up with as a possible solution, thanks!