If a credential is expired, that throws an error here:
|
_checkCredential({credential, log, now}); |
which isn't caught before the next few lines - which check status - can run.
So status doesn't get checked, but should. Otherwise the verifier UI can only show no status or status false, both of which are wrong and misleadingly.
I think we need to move the status check before the expiry check (i.e, before the _checkCredential call.
This should be done as part of digitalcredentials/verifier-core#3
If a credential is expired, that throws an error here:
vc/lib/index.js
Line 359 in 5eeabad
which isn't caught before the next few lines - which check status - can run.
So status doesn't get checked, but should. Otherwise the verifier UI can only show no status or status false, both of which are wrong and misleadingly.
I think we need to move the status check before the expiry check (i.e, before the _checkCredential call.
This should be done as part of digitalcredentials/verifier-core#3