hiero-ledger/hiero-sdk-js

🐥 Beginner Friendly This issue is a great fit for contributors who are ready to explore the Hiero JavaScript codebase a little more and take on slightly more independent work. We strongly recommend completing a Good First Issue before tackling a Beginner Issue. Unlike a Good First Issue, this one does not spell out every line. You will read the existing code, decide which test cases are needed and write them yourself. The description below lists everything that must be covered and points you to the right files. 👾 Description of the Issue src/transaction/List.js is a small internal list class (about 170 lines) that the SDK uses to hold node account IDs and transaction IDs. It can be locked against changes and hands out its items in round-robin order (next, current, advance()). Executable, SignatureMap and FileAppendTransaction depend on it. It has two problems: No unit tests. The class is only tested indirectly. Four ESLint warnings in its JSDoc. Run npx eslint src/transaction/Li

🐥 Beginner Friendly This issue is a great fit for contributors who are ready to explore the Hiero JavaScript codebase a little more and take on slightly more independent work. We strongly recommend completing a Good First Issue before tackling a Beginner Issue. Unlike a Good First Issue, this one does not spell out every line. You will read the existing code, decide which test cases are needed and write them yourself. The description below lists everything that must be covered and points you to the right files. 👾 Description of the Issue When a transaction fails, the SDK throws one of these errors, and they are what SDK users catch and log: src/StatusError.js: the base class. It stores the status and transactionId, and provides toJSON(), toString() and valueOf(). src/PrecheckStatusError.js: thrown when a node rejects a transaction before it reaches consensus. It adds nodeId and contractFunctionResult, builds its own message and overrides toJSON(). src/ReceiptStatusError.js: thro

🐥 Beginner Friendly This issue is a great fit for contributors who are ready to explore the Hiero JavaScript codebase a little more and take on slightly more independent work. We strongly recommend completing a Good First Issue before tackling a Beginner Issue. Unlike a Good First Issue, this one does not spell out every line. You will read the existing code, decide which test cases are needed and write them yourself. The description below lists everything that must be covered and points you to the right files. 👾 Description of the Issue src/encoding/rlpNumber.js contains four small helper functions that convert numbers between the forms SDK users pass in (number, bigint, Long, BigNumber, decimal or hex strings, bytes) and the minimal big-endian bytes that Ethereum transactions store. EthereumTransactionData, Authorization and AccessListItem all rely on them. The module has no unit tests of its own. It is only exercised indirectly, so a regression in an edge case (a leading zero

🆕🐥 First-Time Friendly This issue is especially welcoming for people who are new to contributing to the Hiero JS SDK. We know that opening your first pull request can feel like a big step. Issues labeled Good First Issue are designed to make that experience easier, clearer, and more comfortable. No prior knowledge of Hiero, Hedera, or distributed ledger technology is required. Just a basic familiarity with JavaScript and Git is more than enough to get started. 👾 Description of the Issue src/network/NetworkVersionInfo.js has no unit tests. It is the result of NetworkVersionInfoQuery: a small, immutable value class that holds two SemanticVersion objects, the version of the protobuf API (protobufVersion) and the version of the network services (servicesVersion). SemanticVersion already has tests in test/unit/network/SemanticVersion.js, so this issue completes the pair. The whole class is about 80 lines, and this is everything it does: export default class NetworkVersionInfo {

🆕🐥 First-Time Friendly This issue is especially welcoming for people who are new to contributing to the Hiero JS SDK. We know that opening your first pull request can feel like a big step. Issues labeled Good First Issue are designed to make that experience easier, clearer, and more comfortable. No prior knowledge of Hiero, Hedera, or distributed ledger technology is required. Just a basic familiarity with JavaScript and Git is more than enough to get started. 👾 Description of the Issue The scripts in the examples/ folder show developers how to use the SDK, and some of them print their results to the console. Eleven examples contain spelling mistakes in comments and in printed messages (17 lines in total): Misspelled Correct Where transction transaction 8 console messages in 4 token examples INTIAL INITIAL 2 comments OEPRATIONS OPERATIONS 2 comments submiting submitting 1 comment accound id account ID 2 comments acount account 2 comments Fixing them makes t