Closed LiranCohen closed 3 weeks ago
Latest commit: 1a31231d37d06e76f7d300ceb12151b869a57739
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
TBDocs Report
🛑 Errors: 0 ⚠️ Warnings: 5
packages/api/src/index.ts
packages/crypto/src/index.ts
📄 File: ./packages/crypto/src/utils.ts |
---|
⚠️ extractor:typedoc:missing-docs : CryptoUtils (Variable) does not have any documentation. |
⚠️ extractor:typedoc:missing-docs : CryptoUtils.__type.randomPin (Property) does not have any documentation. |
⚠️ extractor:typedoc:missing-docs : CryptoUtils.__type.randomUuid (Property) does not have any documentation. |
⚠️ extractor:typedoc:missing-docs : CryptoUtils.__type.randomBytes (Property) does not have any documentation. |
⚠️ extractor:typedoc:missing-docs : CryptoUtils.__type.getJoseSignatureAlgorithmFromPublicKey (Property) does not have any documentation. |
packages/crypto-aws-kms/src/index.ts
packages/dids/src/index.ts
packages/credentials/src/index.ts
TBDocs Report Updated at 2024-09-06T18:36:26Z 1a31231
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 93.43%. Comparing base (
da3630a
) to head (1a31231
). Report is 1 commits behind head on main.
stopSync
now blocks if a current sync is in progress before clearing the interval. An optional timeout can be defined, the default is 2 seconds. After this timeout it will throw.TestHarness has been updated to stop sync before clearing storage, previously this caused an issue where an ongoing sync would attempt to sign messages for DID that no longer had keys after clearing storage.
https://github.com/TBD54566975/web5-js/issues/890 has been created to better address this by creating a signal to gracefully stop sync immediately.