style: 2021-09-20 linter warnings batch 25 / 26

[petermetz]

style: 2021-09-20 linter warnings batch 25 / 26

Description

Fix the linter errors in the Fabric Test Ledger class (packages/cactus-test-tooling/src/main/typescript/fabric/fabric-test-ledger-v1.ts)

Acceptance Criteria

1. Each linter warning is either fixed or a specific new issue is created aimed at exactly that one linter warning where applicable: If fixing a linter warning requires a larger refactoring of the codebase, then it is justifiable to break it out into it's own GH task.
2. The pull request submitted links to all (if any) additional issues that were created for the linter warnings that did not fit in the scope of the issue.

Full List of Linter Warnings

packages/cactus-test-tooling/src/main/typescript/fabric/fabric-test-ledger-v1.ts
190:52 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
292:52 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
396:67 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
535:14 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
588:28 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
644:30 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
776:25 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
830:29 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
866:34 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
1319:15 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any

[yayoiukai2021]

can you add me on this one too? Thank you!

[petermetz]

@yayoiukai2021 Yup, assigned it just now, thank you in advance for the contribution!

[petermetz]

Reassigning due to inactivity.

[anrami]

i want to work on this

[yayoiukai2021]

Pleaase do From: Andrew Ramirez ***@***.***> Date: Monday, June 13, 2022 at 10:14 AM To: hyperledger/cactus ***@***.***> Cc: Ukai, Yayoi ***@***.***>, Mention ***@***.***> Subject: Re: [hyperledger/cactus] style: 2021-09-20 linter warnings batch 25 / 26 (#1374) i want to work on this — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/hyperledger/cactus/issues/1374*issuecomment-1154176804__;Iw!!JmoZiZGBv3RvKRSx!4YPc8zHfYwOiWL7knEUMHVtWrVufZcLL7hsX0FRPHk9iJ-EkM0GNzFPxHOn7I5M3IGHeTdgRcaoOSufEyDeb5m6R$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AV4AHDFR4LXKL3XQM6TXCGDVO5T5ZANCNFSM5EMWXMZA__;!!JmoZiZGBv3RvKRSx!4YPc8zHfYwOiWL7knEUMHVtWrVufZcLL7hsX0FRPHk9iJ-EkM0GNzFPxHOn7I5M3IGHeTdgRcaoOSufEyDkfoRkN$>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[petermetz]

Closing due to the linter numbers having gone stale in the meantime.
We need to invent a better way of tracking linter warnings for future issues like this that we'll open because the line numbers are ephemeral and therefore not well suited for this.

Please see these if you'd still like to work on linter warnings that are beginner-friendly:
https://github.com/hyperledger/cacti/issues/2674
https://github.com/hyperledger/cacti/issues/2675