Closed PhilippeR26 closed 1 week ago
@PhilippeR26 let me hop on this
@EjembiEmmanuel Feel free to jump onto this one if you can figure it out.
'index$2' do contain RPC on final build so I am not sure what is the issue here. The only workaround until we figure it out is to use starknet-types directly
import { SPEC } from 'starknet-types';
async function main() {
const a: SPEC.SIERRA_ENTRY_POINT = { selector: '0x123', function_idx: 2 };
:tada: This issue has been resolved in version 6.10.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 7.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Describe the bug 2 problems encountered :
1. No Vscode help in RPC spacename
Reading the Starknet.js code, I understand that the paths to use the enums located in src/types/api/rpcspec_0_6/nonspec.ts or in spec 07 are :
Long and complicated path.... but it works. After typing
types.
, vsCode is helping to reachRPC
: But after selectingRPC
, there is no more help from vsCode : There it becomes complicated. Only digging in a very nested source code can help you.2. use of RPC types
If you add to the previous code :
The compilation fails :
So, how to use these types?
To Reproduce See above
Expected behavior Good user experience to use RPC enums. Have a way to use types of RPC.
Screenshots See above.
Desktop (please complete the following information):
Additional context