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.

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

Use valid json for multicalls #2502

Open
cptartur opened this issue Sep 23, 2024 · 0 comments
Open

Use valid json for multicalls #2502

cptartur opened this issue Sep 23, 2024 · 0 comments
Labels
feature New feature request/description sncast

Comments

@cptartur
Copy link
Member

cptartur commented Sep 23, 2024

The contents of multicall file should be a valid json file as per specification.

This change should be backward compatible. It should (for the time being) be possible to use the old multicall file format (e.g. through a flag in cli). We should deprecate the old format and issue warnings when new format is being used.

@cptartur cptartur converted this from a draft issue Sep 23, 2024
@github-actions github-actions bot added the new label Sep 23, 2024
@cptartur cptartur added sncast feature New feature request/description and removed new labels Sep 23, 2024
@cptartur cptartur moved this from Backlog to Triage in Starknet foundry Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature request/description sncast
Projects
Status: Triage
Development

No branches or pull requests

1 participant