@cfxjs/sirius-next-i18n 0.2.12 → 0.2.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,4 +1,4 @@
1
1
 
2
- > @cfxjs/sirius-next-i18n@0.2.12 build /home/runner/work/sirius-next/sirius-next/packages/i18n
2
+ > @cfxjs/sirius-next-i18n@0.2.14 build /home/runner/work/sirius-next/sirius-next/packages/i18n
3
3
  > tsc
4
4
 
@@ -267,8 +267,7 @@
267
267
  "notVerifyImplementContract": "Read / Write as Proxy function is available after the proxy and implementation <0>contract verification.</0>",
268
268
  "pattern": "ABI for the implementation contract at <0>address</0>, using <1>pattern</1> proxy pattern.",
269
269
  "beacon": {
270
- "pattern1": "ABI for the implementation contract at <1>address</1> using the <3>EIP-1967 Beacon Proxy</3> pattern.",
271
- "pattern2": "Previously recorded to be associated with beacon contract on <1>address</1> ."
270
+ "pattern1": "This proxy contract uses the <1>EIP-1967 Beacon Proxy</1> pattern. Its current implementation contract is <3>address</3>, and its Beacon contract is <5>address</5>."
272
271
  },
273
272
  "expandAll": "Expand All",
274
273
  "reset": "Reset",
@@ -286,7 +285,10 @@
286
285
  "tupleArray": "Please enter a valid tuple (JSON array or object that conforms to the parameter order and format) array",
287
286
  "notSupport": "{{type}} support will be coming soon"
288
287
  },
289
- "tupleFormat": "Tuple type:<code>{{type}}</code><br />Parameter name:<code>{{params}}</code><br />Tuple parameter array:<code>{{paramsArray}}</code><br />Tuple parameter object:<code>{{paramsObject}}</code>",
288
+ "tupleType": "Tuple type",
289
+ "tupleParameterName": "Parameter name:",
290
+ "tupleParameterArray": "Tuple parameter array:",
291
+ "tupleParameterObject": "Tuple parameter object:",
290
292
  "tupleTips": "Remark: You can refer to <code>Tuple parameter array</code> or <code>Tuple parameter object</code> for tuple input.<br />Tuple input format should be a <code>JSON array or object</code> that is legal and conforms to the order and format of the parameters. For example, tuple is declared as <code>{ uint num; string str; }</code>, then the tuple input format should be: <code>[1, \"text\"]</code> or <code>{ \"num\": 1, \"str\": \"text\" }</code>. <br />For nested tuples, the input format should be <code>nested JSON array or object</code> that are legal and conform to the parameter order and format. For example, tuples declared as <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>, the tuple B input format should be: <code>[1, [\"Tom\", 28]]</code> or <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>.",
291
293
  "query": "Query",
292
294
  "write": "Write",
@@ -266,8 +266,7 @@
266
266
  "notVerifyImplementContract": "在代理合约和执行合约均被<0>验证</0>后可使用代理合约的读写功能。",
267
267
  "pattern": "实现执行合约的 ABI 位于 <0>address</0>, 使用 <1>pattern</1> 代理模式.",
268
268
  "beacon": {
269
- "pattern1": "实现执行合约的 ABI 位于 <1>address</1> ,采用的是 <3>EIP-1967 Beacon Proxy</3> 模式。",
270
- "pattern2": "该合约此前记录对应的 beacon 合约为 <1>address</1> 。"
269
+ "pattern1": "该代理合约采用 <1>EIP-1967 Beacon Proxy</1> 模式,当前实现合约为 <3>address</3>,Beacon 合约为 <5>address</5>。"
271
270
  },
272
271
  "expandAll": "全部展开",
273
272
  "reset": "重置",
@@ -285,7 +284,10 @@
285
284
  "tupleArray": "请输入有效的元组(符合参数顺序和格式的 json 数组或对象)数组",
286
285
  "notSupport": "{{type}} 即将支持,敬请期待"
287
286
  },
288
- "tupleFormat": "元组类型:<code>{{type}}</code><br />参数名称:<code>{{params}}</code><br />元组参数数组:<code>{{paramsArray}}</code><br />元组参数对象:<code>{{paramsObject}}</code>",
287
+ "tupleType": "元组类型:",
288
+ "tupleParameterName": "参数名称:",
289
+ "tupleParameterArray": "元组参数数组:",
290
+ "tupleParameterObject": "元组参数对象:",
289
291
  "tupleTips": "提示:可以参考 <code>元组参数数组</code> 或 <code>元组参数对象</code> 进行元组参数输入。<br />元组输入格式应为合法并符合参数顺序和格式的 <code>JSON 数组或对象</code>,例如:元组声明为 <code>{ uint num; string str; }</code>,则元组输入格式应为:<code>[1, \"text\"]</code> 或 <code>{ \"num\": 1, \"str\": \"text\" }</code>。<br />对于嵌套的元组,输入格式应为合法并符合参数顺序和格式的 <code>嵌套的 JSON 数组或对象</code>,例如:元组声明为 <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>,则元组 B 输入格式应为:<code>[1, [\"Tom\", 28]]</code> 或 <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>。",
290
292
  "query": "读取",
291
293
  "write": "写入",
@@ -267,8 +267,7 @@
267
267
  "notVerifyImplementContract": "Read / Write as Proxy function is available after the proxy and implementation <0>contract verification.</0>",
268
268
  "pattern": "ABI for the implementation contract at <0>address</0>, using <1>pattern</1> proxy pattern.",
269
269
  "beacon": {
270
- "pattern1": "ABI for the implementation contract at <1>address</1> using the <3>EIP-1967 Beacon Proxy</3> pattern.",
271
- "pattern2": "Previously recorded to be associated with beacon contract on <1>address</1> ."
270
+ "pattern1": "This proxy contract uses the <1>EIP-1967 Beacon Proxy</1> pattern. Its current implementation contract is <3>address</3>, and its Beacon contract is <5>address</5>."
272
271
  },
273
272
  "expandAll": "Expand All",
274
273
  "reset": "Reset",
@@ -286,7 +285,10 @@
286
285
  "tupleArray": "Please enter a valid tuple (JSON array or object that conforms to the parameter order and format) array",
287
286
  "notSupport": "{{type}} support will be coming soon"
288
287
  },
289
- "tupleFormat": "Tuple type:<code>{{type}}</code><br />Parameter name:<code>{{params}}</code><br />Tuple parameter array:<code>{{paramsArray}}</code><br />Tuple parameter object:<code>{{paramsObject}}</code>",
288
+ "tupleType": "Tuple type",
289
+ "tupleParameterName": "Parameter name:",
290
+ "tupleParameterArray": "Tuple parameter array:",
291
+ "tupleParameterObject": "Tuple parameter object:",
290
292
  "tupleTips": "Remark: You can refer to <code>Tuple parameter array</code> or <code>Tuple parameter object</code> for tuple input.<br />Tuple input format should be a <code>JSON array or object</code> that is legal and conforms to the order and format of the parameters. For example, tuple is declared as <code>{ uint num; string str; }</code>, then the tuple input format should be: <code>[1, \"text\"]</code> or <code>{ \"num\": 1, \"str\": \"text\" }</code>. <br />For nested tuples, the input format should be <code>nested JSON array or object</code> that are legal and conform to the parameter order and format. For example, tuples declared as <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>, the tuple B input format should be: <code>[1, [\"Tom\", 28]]</code> or <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>.",
291
293
  "query": "Query",
292
294
  "write": "Write",
@@ -257,8 +257,7 @@
257
257
  "notVerifyImplementContract": "Read / Write as Proxy function is available after the proxy and implementation <0>contract verification.</0>",
258
258
  "pattern": "ABI for the implementation contract at <0>address</0>, using <1>pattern</1> proxy pattern.",
259
259
  "beacon": {
260
- "pattern1": "ABI for the implementation contract at <1>address</1> using the <3>EIP-1967 Beacon Proxy</3> pattern.",
261
- "pattern2": "Previously recorded to be associated with beacon contract on <1>address</1> ."
260
+ "pattern1": "This proxy contract uses the <1>EIP-1967 Beacon Proxy</1> pattern. Its current implementation contract is <3>address</3>, and its Beacon contract is <5>address</5>."
262
261
  },
263
262
  "expandAll": "Expand All",
264
263
  "reset": "Reset",
@@ -276,7 +275,10 @@
276
275
  "tupleArray": "Please enter a valid tuple (JSON array or object that conforms to the parameter order and format) array",
277
276
  "notSupport": "{{type}} support will be coming soon"
278
277
  },
279
- "tupleFormat": "Tuple type:<code>{{type}}</code><br />Parameter name:<code>{{params}}</code><br />Tuple parameter array:<code>{{paramsArray}}</code><br />Tuple parameter object:<code>{{paramsObject}}</code>",
278
+ "tupleType": "Tuple type",
279
+ "tupleParameterName": "Parameter name:",
280
+ "tupleParameterArray": "Tuple parameter array:",
281
+ "tupleParameterObject": "Tuple parameter object:",
280
282
  "tupleTips": "Remark: You can refer to <code>Tuple parameter array</code> or <code>Tuple parameter object</code> for tuple input.<br />Tuple input format should be a <code>JSON array or object</code> that is legal and conforms to the order and format of the parameters. For example, tuple is declared as <code>{ uint num; string str; }</code>, then the tuple input format should be: <code>[1, \"text\"]</code> or <code>{ \"num\": 1, \"str\": \"text\" }</code>. <br />For nested tuples, the input format should be <code>nested JSON array or object</code> that are legal and conform to the parameter order and format. For example, tuples declared as <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>, the tuple B input format should be: <code>[1, [\"Tom\", 28]]</code> or <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>.",
281
283
  "query": "Query",
282
284
  "write": "Write",
@@ -257,8 +257,7 @@
257
257
  "notVerifyImplementContract": "Read / Write as Proxy function is available after the proxy and implementation <0>contract verification.</0>",
258
258
  "pattern": "ABI for the implementation contract at <0>address</0>, using <1>pattern</1> proxy pattern.",
259
259
  "beacon": {
260
- "pattern1": "ABI for the implementation contract at <1>address</1> using the <3>EIP-1967 Beacon Proxy</3> pattern.",
261
- "pattern2": "Previously recorded to be associated with beacon contract on <1>address</1> ."
260
+ "pattern1": "This proxy contract uses the <1>EIP-1967 Beacon Proxy</1> pattern. Its current implementation contract is <3>address</3>, and its Beacon contract is <5>address</5>."
262
261
  },
263
262
  "expandAll": "Expand All",
264
263
  "reset": "Reset",
@@ -276,7 +275,10 @@
276
275
  "tupleArray": "Please enter a valid tuple (JSON array or object that conforms to the parameter order and format) array",
277
276
  "notSupport": "{{type}} support will be coming soon"
278
277
  },
279
- "tupleFormat": "Tuple type:<code>{{type}}</code><br />Parameter name:<code>{{params}}</code><br />Tuple parameter array:<code>{{paramsArray}}</code><br />Tuple parameter object:<code>{{paramsObject}}</code>",
278
+ "tupleType": "Tuple type",
279
+ "tupleParameterName": "Parameter name:",
280
+ "tupleParameterArray": "Tuple parameter array:",
281
+ "tupleParameterObject": "Tuple parameter object:",
280
282
  "tupleTips": "Remark: You can refer to <code>Tuple parameter array</code> or <code>Tuple parameter object</code> for tuple input.<br />Tuple input format should be a <code>JSON array or object</code> that is legal and conforms to the order and format of the parameters. For example, tuple is declared as <code>{ uint num; string str; }</code>, then the tuple input format should be: <code>[1, \"text\"]</code> or <code>{ \"num\": 1, \"str\": \"text\" }</code>. <br />For nested tuples, the input format should be <code>nested JSON array or object</code> that are legal and conform to the parameter order and format. For example, tuples declared as <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>, the tuple B input format should be: <code>[1, [\"Tom\", 28]]</code> or <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>.",
281
283
  "query": "Query",
282
284
  "write": "Write",
@@ -256,8 +256,7 @@
256
256
  "notVerifyImplementContract": "在代理合约和执行合约均被<0>验证</0>后可使用代理合约的读写功能。",
257
257
  "pattern": "实现执行合约的 ABI 位于 <0>address</0>, 使用 <1>pattern</1> 代理模式.",
258
258
  "beacon": {
259
- "pattern1": "实现执行合约的 ABI 位于 <1>address</1> ,采用的是 <3>EIP-1967 Beacon Proxy</3> 模式。",
260
- "pattern2": "该合约此前记录对应的 beacon 合约为 <1>address</1> 。"
259
+ "pattern1": "该代理合约采用 <1>EIP-1967 Beacon Proxy</1> 模式,当前实现合约为 <3>address</3>,Beacon 合约为 <5>address</5>。"
261
260
  },
262
261
  "expandAll": "全部展开",
263
262
  "reset": "重置",
@@ -275,7 +274,10 @@
275
274
  "tupleArray": "请输入有效的元组(符合参数顺序和格式的 json 数组或对象)数组",
276
275
  "notSupport": "{{type}} 即将支持,敬请期待"
277
276
  },
278
- "tupleFormat": "元组类型:<code>{{type}}</code><br />参数名称:<code>{{params}}</code><br />元组参数数组:<code>{{paramsArray}}</code><br />元组参数对象:<code>{{paramsObject}}</code>",
277
+ "tupleType": "元组类型:",
278
+ "tupleParameterName": "参数名称:",
279
+ "tupleParameterArray": "元组参数数组:",
280
+ "tupleParameterObject": "元组参数对象:",
279
281
  "tupleTips": "提示:可以参考 <code>元组参数数组</code> 或 <code>元组参数对象</code> 进行元组参数输入。<br />元组输入格式应为合法并符合参数顺序和格式的 <code>JSON 数组或对象</code>,例如:元组声明为 <code>{ uint num; string str; }</code>,则元组输入格式应为:<code>[1, \"text\"]</code> 或 <code>{ \"num\": 1, \"str\": \"text\" }</code>。<br />对于嵌套的元组,输入格式应为合法并符合参数顺序和格式的 <code>嵌套的 JSON 数组或对象</code>,例如:元组声明为 <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>,则元组 B 输入格式应为:<code>[1, [\"Tom\", 28]]</code> 或 <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>。",
280
282
  "query": "读取",
281
283
  "write": "写入",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cfxjs/sirius-next-i18n",
3
- "version": "0.2.12",
3
+ "version": "0.2.14",
4
4
  "files": [
5
5
  "*/**"
6
6
  ],