fix: typescript fix getNetwork() return type

[PierreJeanjacquot]

No description provided.

[github-actions]

🐳 Hadolint Dockerfile Lint Results

Click to expand detailed results

Dockerfile:18 DL3059 info: Multiple consecutive `RUN` instructions. Consider consolidation.
Dockerfile:19 DL3016 warning: Pin versions in npm. Instead of `npm install <package>` use `npm install <package>@<version>`
Dockerfile:19 DL3059 info: Multiple consecutive `RUN` instructions. Consider consolidation.

[abbesBenayache]

LGTM

[Copilot]

Pull Request Overview

Updates the documentation to reflect that getNetwork() now returns chainId as a string rather than a number.

• Changed return type of getNetwork signature from number to string
• Updated both the inline signature and the Returns section in the docs

Comments suppressed due to low confidence (2)

docs/classes/IExecNetworkModule.md:67

• [nitpick] The markdown formatting escapes the '>' and splits the code into multiple spans, which can be hard to read. Consider wrapping the entire return type in a single code span, e.g., Promise<{ chainId: string; isNative: boolean }>, and remove the escape.

▸ **getNetwork**(): `Promise`<{ `chainId`: `string` ; `isNative`: `boolean`  }\>

docs/classes/IExecNetworkModule.md:81

• [nitpick] Similarly for the Returns section, wrap the full signature in one code span: Promise<{ chainId: string; isNative: boolean }> and remove the unnecessary escape for '>.'

`Promise`<{ `chainId`: `string` ; `isNative`: `boolean`  }\>

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud