Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Entry point vs entrypoint naming incosistency #276

Open
FabijanC opened this issue Feb 7, 2025 · 0 comments
Open

Entry point vs entrypoint naming incosistency #276

FabijanC opened this issue Feb 7, 2025 · 0 comments

Comments

@FabijanC
Copy link
Contributor

FabijanC commented Feb 7, 2025

As of v0.8.0-rc.3, only the ENTRYPOINT_NOT_FOUND error (in starknet_api_openrpc.json) and INVOKE_CALL.calldata.description (in wallet_rpc.json) have the joint version of spelling ("entrypoint"), as opposed to the vast majority of other occurrences using the split spelling of "entry point".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FabijanC