Add Simplified Chinese translations for EVM Developers section#51
Add Simplified Chinese translations for EVM Developers section#51
Conversation
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 10
🤖 Fix all issues with AI agents
In @.gitbook/cn/developers-evm/add-injective-to-your-dapp.mdx:
- Around line 17-27: Update the INJECTIVE_MAINNET_CONFIG object so its rpcUrls
and blockExplorerUrls use the canonical endpoints: replace rpcUrls entry in
INJECTIVE_MAINNET_CONFIG with "https://sentry.evm-rpc.injective.network/" and
replace blockExplorerUrls entry with "https://blockscout.injective.network/";
ensure the rest of INJECTIVE_MAINNET_CONFIG (chainId, chainName, nativeCurrency,
decimals) remains unchanged so examples and other guides stay consistent.
In @.gitbook/cn/developers-evm/dapps/connect-with-metamask.mdx:
- Around line 213-224: The properties used in the wallet_addEthereumChain
request are incorrect; update the params object to use the actual fields on
INJECTIVE_EVM_PARAMS: use INJECTIVE_EVM_PARAMS.chainId (not chainHex),
INJECTIVE_EVM_PARAMS.rpcUrls (array, not rpcUrl), and
INJECTIVE_EVM_PARAMS.blockExplorerUrls (array, not blockExplorer), keeping
chainName and nativeCurrency as-is so the call to window.ethereum.request({
method: 'wallet_addEthereumChain', params: [...] }) matches the defined
INJECTIVE_EVM_PARAMS shape.
- Around line 270-274: The code uses an undefined variable injectiveEvm when
creating the publicClient; replace it with the correct viem chain configuration
(e.g., INJECTIVE_EVM_PARAMS) or first convert INJECTIVE_EVM_PARAMS to a viem
Chain via defineChain before passing to createPublicClient; update the const
publicClient = createPublicClient({ chain:
<use-INJECTIVE_EVM_PARAMS-or-defineChain-result>, transport: http() }) so
createPublicClient receives a valid viem Chain object.
In @.gitbook/cn/developers-evm/dapps/connect-with-walletconnect.mdx:
- Around line 38-40: The block explorer entry in the blockExplorers object
includes a trailing "/blocks" path which will break URL generation; update the
default InjectiveScan entry (blockExplorers.default with name 'InjectiveScan'
and url) to use the base explorer URL without the "/blocks" suffix (e.g.
'https://testnet.blockscout.injective.network') so transaction/address links are
constructed correctly.
- Line 73: The import path for wagmiConfig in connect-with-walletconnect.mdx is
inconsistent with the earlier example; update the import so that the wagmiConfig
symbol is imported from the same module shown earlier (the lib/wagmi module) or,
alternatively, change the earlier example to reference ./providers so both
examples match; locate the wagmiConfig import in this MDX and make the path
consistent with the existing lib/wagmi usage.
In @.gitbook/cn/developers-evm/evm-integrations-faq.mdx:
- Around line 30-31: 将开头短语“阅读更多关于 MTS 的信息：”替换为更通顺的中文，例如“更多关于 MTS 的信息：”或“阅读更多有关
MTS 的信息：”；在该文件中查找原始文本“阅读更多关于 MTS 的信息：”并用推荐替代句之一替换以修正 LanguageTool 标记的措辞问题。
In @.gitbook/cn/developers-evm/network-information.mdx:
- Line 61: Replace the incorrect HTTP scheme on the Testnet WebSocket endpoint
string `https://k8s.testnet.ws.injective.network/` with the secure WebSocket
scheme `wss://k8s.testnet.ws.injective.network/`; locate the WS Endpoint line in
the network-information.mdx content and update that literal so it matches the
Mainnet format (`wss://...`) to ensure the WebSocket URL uses the wss://
protocol.
In @.gitbook/cn/developers-evm/smart-contracts/test-hardhat.mdx:
- Around line 24-31: The test assigns to an undeclared variable `Counter` inside
the `before` hook which triggers a ReferenceError in strict mode; declare the
contract factory locally (e.g., change the assignment in the `before` function
to use `const Counter = await ethers.getContractFactory('Counter')`) so
`Counter` is properly declared and `counter = await Counter.deploy()` continues
to work.
In @.gitbook/cn/developers-evm/wrapped-inj.mdx:
- Line 104: Locate the sentence "请注意，INJ 增加会略少一些，因为它用于支付交易费用。" and simplify the
redundant phrasing by replacing "略少一些" with a concise form such as "略少" (result:
"请注意，INJ 增加会略少，因为它用于支付交易费用。"); update the line in
.gitbook/cn/developers-evm/wrapped-inj.mdx accordingly.
- Line 93: The sentence "请注意，INJ 减少会略多一些，因为它用于支付交易费用。" has a redundant phrase
"略多一些"; change it to a concise form such as "会略多" or "会多一些" (e.g., "请注意，INJ
减少会略多，因为它用于支付交易费用。") to remove redundancy while preserving meaning; update the
text in the wrapped-inj.mdx line containing that sentence.
🧹 Nitpick comments (6)
.gitbook/cn/developers-evm/smart-contracts/verify-hardhat.mdx (1)
24-24: Resolve or track the inline TODO before publishing.Leaving TODOs in docs can get missed; either move the section to FAQs now or remove the TODO and track it elsewhere.
🧹 Suggested cleanup
-{/* TODO consider moving this section to FAQs */}Want me to draft the FAQ entry or open a tracking issue?
.gitbook/cn/developers-evm/smart-contracts/verify-foundry.mdx (1)
24-24: Resolve or track the inline TODO before publishing.Same note as the Hardhat page — please remove or move to FAQs and track it externally.
🧹 Suggested cleanup
-{/* TODO consider moving this section to FAQs */}Want me to draft the FAQ entry or open a tracking issue?
.gitbook/cn/developers-evm/dapps/connect-with-metamask.mdx (1)
253-254: Unused imports in viem example.
defineChainandformatEtherare imported but never used in the code sample.♻️ Proposed fix
import { counterAbi } from './abi/counterAbi' import { INJECTIVE_EVM_PARAMS } from './config' import { createPublicClient, http } from 'viem' -import { createWalletClient, custom, defineChain, formatEther } from 'viem' +import { createWalletClient, custom } from 'viem'.gitbook/cn/developers-evm/multivm-token-standard.mdx (2)
49-49: Inconsistent link language: English path in Chinese documentation.The link
/developers-native/injective/tokenfactory/points to English documentation while this is a Chinese documentation file. If a Chinese translation exists for Token Factory, consider updating to/cn/developers-native/injective/tokenfactory/. If no Chinese version exists, consider adding a note indicating the link leads to English documentation.
66-66: Another link pointing to English documentation.Similar to the Token Factory link,
/developers-native/core/points to English documentation..gitbook/cn/developers-evm/dapps/connect-with-walletconnect.mdx (1)
72-72: Unused import:Imagefrom 'next/image'.The
Imagecomponent is imported but never used in this file.Suggested fix
-import Image from 'next/image'
| const INJECTIVE_MAINNET_CONFIG = { | ||
| chainId: '0x6f0', // 十进制 1776 | ||
| chainName: 'Injective', | ||
| rpcUrls: ['https://evm-rpc.injective.network'], | ||
| nativeCurrency: { | ||
| name: 'Injective', | ||
| symbol: 'INJ', | ||
| decimals: 18 | ||
| }, | ||
| blockExplorerUrls: ['https://explorer.injective.network'] | ||
| }; |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, check if the files exist and locate network-information.mdx
find .gitbook/cn -name "*network-information*" -o -name "*add-injective*"Repository: InjectiveLabs/injective-docs
Length of output: 180
🏁 Script executed:
# Run the verification script from the review comment
echo "=== RPC URL variations ==="
rg -n "evm-rpc\.injective\.network" .gitbook/cn/
echo ""
echo "=== Explorer URL variations ==="
rg -n "blockscout\.injective\.network|explorer\.injective\.network" .gitbook/cn/Repository: InjectiveLabs/injective-docs
Length of output: 5113
🏁 Script executed:
# Also check the specific file mentioned in the review
echo "=== Content of add-injective-to-your-dapp.mdx (lines 17-27) ==="
cat -n .gitbook/cn/developers-evm/add-injective-to-your-dapp.mdx | head -30Repository: InjectiveLabs/injective-docs
Length of output: 1021
🏁 Script executed:
# Search for network-information file more broadly
find .gitbook/cn -type f -name "*.mdx" | xargs grep -l "sentry.evm-rpc.injective.network"Repository: InjectiveLabs/injective-docs
Length of output: 182
Update RPC and block explorer URLs to match the canonical endpoints in network-information.mdx.
The current configuration uses non-standard endpoints that differ from the official documentation:
- RPC URL: Should be
https://sentry.evm-rpc.injective.network/(nothttps://evm-rpc.injective.network) - Block Explorer: Should be
https://blockscout.injective.network/(nothttps://explorer.injective.network)
These incorrect endpoints will cause integration failures for developers following this guide. Update lines 20 and 26 to use the canonical endpoints documented in network-information.mdx and consistent with other integration guides like evm-integrations-cheat-sheet.mdx.
🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/add-injective-to-your-dapp.mdx around lines 17 -
27, Update the INJECTIVE_MAINNET_CONFIG object so its rpcUrls and
blockExplorerUrls use the canonical endpoints: replace rpcUrls entry in
INJECTIVE_MAINNET_CONFIG with "https://sentry.evm-rpc.injective.network/" and
replace blockExplorerUrls entry with "https://blockscout.injective.network/";
ensure the rest of INJECTIVE_MAINNET_CONFIG (chainId, chainName, nativeCurrency,
decimals) remains unchanged so examples and other guides stay consistent.
| await window.ethereum.request({ | ||
| method: 'wallet_addEthereumChain', | ||
| params: [ | ||
| { | ||
| chainId: INJECTIVE_EVM_PARAMS.chainHex, | ||
| chainName: INJECTIVE_EVM_PARAMS.chainName, | ||
| rpcUrls: [INJECTIVE_EVM_PARAMS.rpcUrl], | ||
| nativeCurrency: INJECTIVE_EVM_PARAMS.nativeCurrency, | ||
| blockExplorerUrls: [INJECTIVE_EVM_PARAMS.blockExplorer], | ||
| }, | ||
| ], | ||
| }) |
There was a problem hiding this comment.
Property names do not match the defined config object.
The code references properties (chainHex, rpcUrl, blockExplorer) that don't exist on INJECTIVE_EVM_PARAMS defined earlier (lines 66-76). The actual properties are chainId, rpcUrls (array), and blockExplorerUrls (array). This will cause runtime errors.
🐛 Proposed fix
await window.ethereum.request({
method: 'wallet_addEthereumChain',
params: [
{
- chainId: INJECTIVE_EVM_PARAMS.chainHex,
- chainName: INJECTIVE_EVM_PARAMS.chainName,
- rpcUrls: [INJECTIVE_EVM_PARAMS.rpcUrl],
- nativeCurrency: INJECTIVE_EVM_PARAMS.nativeCurrency,
- blockExplorerUrls: [INJECTIVE_EVM_PARAMS.blockExplorer],
+ chainId: INJECTIVE_EVM_PARAMS.chainId,
+ chainName: INJECTIVE_EVM_PARAMS.chainName,
+ rpcUrls: INJECTIVE_EVM_PARAMS.rpcUrls,
+ nativeCurrency: INJECTIVE_EVM_PARAMS.nativeCurrency,
+ blockExplorerUrls: INJECTIVE_EVM_PARAMS.blockExplorerUrls,
},
],
})📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| await window.ethereum.request({ | |
| method: 'wallet_addEthereumChain', | |
| params: [ | |
| { | |
| chainId: INJECTIVE_EVM_PARAMS.chainHex, | |
| chainName: INJECTIVE_EVM_PARAMS.chainName, | |
| rpcUrls: [INJECTIVE_EVM_PARAMS.rpcUrl], | |
| nativeCurrency: INJECTIVE_EVM_PARAMS.nativeCurrency, | |
| blockExplorerUrls: [INJECTIVE_EVM_PARAMS.blockExplorer], | |
| }, | |
| ], | |
| }) | |
| await window.ethereum.request({ | |
| method: 'wallet_addEthereumChain', | |
| params: [ | |
| { | |
| chainId: INJECTIVE_EVM_PARAMS.chainId, | |
| chainName: INJECTIVE_EVM_PARAMS.chainName, | |
| rpcUrls: INJECTIVE_EVM_PARAMS.rpcUrls, | |
| nativeCurrency: INJECTIVE_EVM_PARAMS.nativeCurrency, | |
| blockExplorerUrls: INJECTIVE_EVM_PARAMS.blockExplorerUrls, | |
| }, | |
| ], | |
| }) |
🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/dapps/connect-with-metamask.mdx around lines 213
- 224, The properties used in the wallet_addEthereumChain request are incorrect;
update the params object to use the actual fields on INJECTIVE_EVM_PARAMS: use
INJECTIVE_EVM_PARAMS.chainId (not chainHex), INJECTIVE_EVM_PARAMS.rpcUrls
(array, not rpcUrl), and INJECTIVE_EVM_PARAMS.blockExplorerUrls (array, not
blockExplorer), keeping chainName and nativeCurrency as-is so the call to
window.ethereum.request({ method: 'wallet_addEthereumChain', params: [...] })
matches the defined INJECTIVE_EVM_PARAMS shape.
| // 创建 PublicClient 用于读取合约状态 | ||
| const publicClient = createPublicClient({ | ||
| chain: injectiveEvm, | ||
| transport: http(), | ||
| }) |
There was a problem hiding this comment.
Undefined variable injectiveEvm in viem example.
Line 272 references injectiveEvm which is never defined. It should likely be INJECTIVE_EVM_PARAMS to match the import on line 252, or a properly defined chain configuration for viem.
🐛 Proposed fix
// 创建 PublicClient 用于读取合约状态
const publicClient = createPublicClient({
- chain: injectiveEvm,
+ chain: INJECTIVE_EVM_PARAMS,
transport: http(),
})Note: If using viem, INJECTIVE_EVM_PARAMS may need to be defined using defineChain() to match viem's expected chain format rather than the EIP-3085 format used for wallet_addEthereumChain.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| // 创建 PublicClient 用于读取合约状态 | |
| const publicClient = createPublicClient({ | |
| chain: injectiveEvm, | |
| transport: http(), | |
| }) | |
| // 创建 PublicClient 用于读取合约状态 | |
| const publicClient = createPublicClient({ | |
| chain: INJECTIVE_EVM_PARAMS, | |
| transport: http(), | |
| }) |
🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/dapps/connect-with-metamask.mdx around lines 270
- 274, The code uses an undefined variable injectiveEvm when creating the
publicClient; replace it with the correct viem chain configuration (e.g.,
INJECTIVE_EVM_PARAMS) or first convert INJECTIVE_EVM_PARAMS to a viem Chain via
defineChain before passing to createPublicClient; update the const publicClient
= createPublicClient({ chain: <use-INJECTIVE_EVM_PARAMS-or-defineChain-result>,
transport: http() }) so createPublicClient receives a valid viem Chain object.
| blockExplorers: { | ||
| default: { name: 'InjectiveScan', url: 'https://testnet.blockscout.injective.network/blocks' }, | ||
| }, |
There was a problem hiding this comment.
Block explorer URL includes /blocks path.
The block explorer base URL typically shouldn't include /blocks. This might cause incorrect URL generation when the explorer constructs transaction or address links.
Suggested fix
blockExplorers: {
- default: { name: 'InjectiveScan', url: 'https://testnet.blockscout.injective.network/blocks' },
+ default: { name: 'InjectiveScan', url: 'https://testnet.blockscout.injective.network' },
},📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| blockExplorers: { | |
| default: { name: 'InjectiveScan', url: 'https://testnet.blockscout.injective.network/blocks' }, | |
| }, | |
| blockExplorers: { | |
| default: { name: 'InjectiveScan', url: 'https://testnet.blockscout.injective.network' }, | |
| }, |
🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/dapps/connect-with-walletconnect.mdx around lines
38 - 40, The block explorer entry in the blockExplorers object includes a
trailing "/blocks" path which will break URL generation; update the default
InjectiveScan entry (blockExplorers.default with name 'InjectiveScan' and url)
to use the base explorer URL without the "/blocks" suffix (e.g.
'https://testnet.blockscout.injective.network') so transaction/address links are
constructed correctly.
| 'use client' | ||
|
|
||
| import Image from 'next/image' | ||
| import { wagmiConfig } from './providers' |
There was a problem hiding this comment.
Import path mismatch with earlier code example.
The import from './providers' doesn't match the file path shown earlier (lib/wagmi.ts at line 47). This inconsistency may confuse developers following the tutorial.
Suggested fix
-import { wagmiConfig } from './providers'
+import { wagmiConfig } from '../lib/wagmi'Or update the earlier code comment to match:
-// lib/wagmi.ts
+// providers.ts🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/dapps/connect-with-walletconnect.mdx at line 73,
The import path for wagmiConfig in connect-with-walletconnect.mdx is
inconsistent with the earlier example; update the import so that the wagmiConfig
symbol is imported from the same module shown earlier (the lib/wagmi module) or,
alternatively, change the earlier example to reference ./providers so both
examples match; locate the wagmiConfig import in this MDX and make the path
consistent with the existing lib/wagmi usage.
| 阅读更多关于 MTS 的信息： | ||
| [一般文章](https://injective.com/blog/multivm-token-standard-wrapped-inj)，和 |
There was a problem hiding this comment.
Polish the “关于” phrasing for smoother Chinese.
LanguageTool flags the current wording; a small tweak reads more naturally.
✍️ Suggested wording
-阅读更多关于 MTS 的信息：
+了解更多有关 MTS 的信息：📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| 阅读更多关于 MTS 的信息： | |
| [一般文章](https://injective.com/blog/multivm-token-standard-wrapped-inj)，和 | |
| 了解更多有关 MTS 的信息： | |
| [一般文章](https://injective.com/blog/multivm-token-standard-wrapped-inj)，和 |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~30-~30: “关于”组成的介词短语必需位于句首，或请改用"对于"代替。
Context: ...e 将来添加其他 VM，MTS token 也将在这些 VM 上工作。 阅读更多关于 MTS 的信息： [一般文章](https://injective.com/b...
(wb2)
🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/evm-integrations-faq.mdx around lines 30 - 31,
将开头短语“阅读更多关于 MTS 的信息：”替换为更通顺的中文，例如“更多关于 MTS 的信息：”或“阅读更多有关 MTS
的信息：”；在该文件中查找原始文本“阅读更多关于 MTS 的信息：”并用推荐替代句之一替换以修正 LanguageTool 标记的措辞问题。
|
|
||
| * Chain ID: `1439` | ||
| * JSON-RPC Endpoint: `https://k8s.testnet.json-rpc.injective.network/` | ||
| * WS Endpoint: `https://k8s.testnet.ws.injective.network/` |
There was a problem hiding this comment.
WebSocket endpoint uses incorrect protocol.
The Testnet WS Endpoint uses https:// instead of wss://. This is inconsistent with the Mainnet WS Endpoint on line 14 which correctly uses wss://. WebSocket endpoints should use the wss:// protocol.
🔧 Proposed fix
-* WS Endpoint: `https://k8s.testnet.ws.injective.network/`
+* WS Endpoint: `wss://k8s.testnet.ws.injective.network`📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| * WS Endpoint: `https://k8s.testnet.ws.injective.network/` | |
| * WS Endpoint: `wss://k8s.testnet.ws.injective.network` |
🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/network-information.mdx at line 61, Replace the
incorrect HTTP scheme on the Testnet WebSocket endpoint string
`https://k8s.testnet.ws.injective.network/` with the secure WebSocket scheme
`wss://k8s.testnet.ws.injective.network/`; locate the WS Endpoint line in the
network-information.mdx content and update that literal so it matches the
Mainnet format (`wss://...`) to ensure the WebSocket URL uses the wss://
protocol.
| describe('Counter', function () { | ||
| let counter; | ||
|
|
||
| before(async function () { | ||
| Counter = await ethers.getContractFactory('Counter'); | ||
| counter = await Counter.deploy(); | ||
| await counter.waitForDeployment(); | ||
| }); |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, let's find and examine the file
find . -name "test-hardhat.mdx" -type fRepository: InjectiveLabs/injective-docs
Length of output: 192
🏁 Script executed:
# Also, let's check the repository structure to understand the context
ls -la .gitbook/ 2>/dev/null || echo "No .gitbook directory at root"Repository: InjectiveLabs/injective-docs
Length of output: 1248
🏁 Script executed:
# Search for hardhat configuration files
fd -e hardhat.config.js -e hardhat.config.ts -e .hardhatrcRepository: InjectiveLabs/injective-docs
Length of output: 54
🏁 Script executed:
# Read the file to see the context around lines 24-31
cat -n ./.gitbook/cn/developers-evm/smart-contracts/test-hardhat.mdx | head -50Repository: InjectiveLabs/injective-docs
Length of output: 1478
🏁 Script executed:
# Also check the English version for comparison
cat -n ./.gitbook/developers-evm/smart-contracts/test-hardhat.mdx | head -50Repository: InjectiveLabs/injective-docs
Length of output: 1941
Declare Counter to avoid a ReferenceError in strict mode.
The code snippet assigns to an undeclared variable, which will throw in Hardhat's strict mode (standard in modern test environments). Use const to properly declare it locally within the before block.
🔧 Suggested fix
- Counter = await ethers.getContractFactory('Counter');
+ const Counter = await ethers.getContractFactory('Counter');🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/smart-contracts/test-hardhat.mdx around lines 24
- 31, The test assigns to an undeclared variable `Counter` inside the `before`
hook which triggers a ReferenceError in strict mode; declare the contract
factory locally (e.g., change the assignment in the `before` function to use
`const Counter = await ethers.getContractFactory('Counter')`) so `Counter` is
properly declared and `counter = await Counter.deploy()` continues to work.
| - 按 "Write" 按钮 | ||
| - 在你的钱包中，确认交易以签名并提交。 | ||
| - 你的钱包应该反映 INJ 减少和 wINJ 增加你选择的金额。 | ||
| - 请注意，INJ 减少会略多一些，因为它用于支付交易费用。 |
There was a problem hiding this comment.
Minor grammar refinement: redundant expression.
"略多一些" contains redundancy - "略" already means "slightly" so "一些" is unnecessary. Consider simplifying to "会略多" or "会多一些".
Suggested fix
- - 请注意，INJ 减少会略多一些，因为它用于支付交易费用。
+ - 请注意，INJ 减少会略多，因为它用于支付交易费用。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - 请注意，INJ 减少会略多一些，因为它用于支付交易费用。 | |
| - 请注意，INJ 减少会略多，因为它用于支付交易费用。 |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~93-~93: ‘略’与‘一些’‘一点’同时使用会造成多余的现象。建议您删除其中一个。
Context: ...映 INJ 减少和 wINJ 增加你选择的金额。 - 请注意，INJ 减少会略多一些，因为它用于支付交易费用。 要将 wINJ 转换为 INJ，在此智能合约上调用...
(s2)
🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/wrapped-inj.mdx at line 93, The sentence "请注意，INJ
减少会略多一些，因为它用于支付交易费用。" has a redundant phrase "略多一些"; change it to a concise form
such as "会略多" or "会多一些" (e.g., "请注意，INJ 减少会略多，因为它用于支付交易费用。") to remove
redundancy while preserving meaning; update the text in the wrapped-inj.mdx line
containing that sentence.
| - 按 "Write" 按钮 | ||
| - 在你的钱包中，确认交易以签名并提交。 | ||
| - 你的钱包应该反映 INJ 增加和 wINJ 减少你选择的金额。 | ||
| - 请注意，INJ 增加会略少一些，因为它用于支付交易费用。 |
There was a problem hiding this comment.
Minor grammar refinement: redundant expression.
Same issue as above - "略少一些" should be simplified.
Suggested fix
- - 请注意，INJ 增加会略少一些，因为它用于支付交易费用。
+ - 请注意，INJ 增加会略少，因为它用于支付交易费用。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - 请注意，INJ 增加会略少一些，因为它用于支付交易费用。 | |
| - 请注意，INJ 增加会略少，因为它用于支付交易费用。 |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~104-~104: ‘略’与‘一些’‘一点’同时使用会造成多余的现象。建议您删除其中一个。
Context: ...映 INJ 增加和 wINJ 减少你选择的金额。 - 请注意，INJ 增加会略少一些，因为它用于支付交易费用。 # 如何通过 Injective Do 使用 wI...
(s2)
🤖 Prompt for AI Agents
In @.gitbook/cn/developers-evm/wrapped-inj.mdx at line 104, Locate the sentence
"请注意，INJ 增加会略少一些，因为它用于支付交易费用。" and simplify the redundant phrasing by replacing
"略少一些" with a concise form such as "略少" (result: "请注意，INJ 增加会略少，因为它用于支付交易费用。");
update the line in .gitbook/cn/developers-evm/wrapped-inj.mdx accordingly.
1 participant
Added language switching functionality to the documentation site with Simplified Chinese as an option. Translated all 24 pages in the EVM Developers section to Simplified Chinese, maintaining technical terms in English and preserving the professional tone.
Files changed:
Created by Mintlify agent
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.