Skip to content
This repository was archived by the owner on Sep 14, 2023. It is now read-only.

ws chain version specificity #534

Open
Tracked by #1077
harrysolovay opened this issue Jan 30, 2023 · 0 comments
Open
Tracked by #1077

ws chain version specificity #534

harrysolovay opened this issue Jan 30, 2023 · 0 comments
Assignees
@tjjfvi
Labels
codegen task

Comments

@harrysolovay
Copy link
Contributor

Currently, whenever there is a runtime upgrade / someone is using a CLI with a version different from that of the given import specifier, an error occurs. The error doesn't necessarily need to occur. How do we want to deal with this?
@tjjfvi tjjfvi mentioned this issue Mar 8, 2023
Closed
@harrysolovay harrysolovay changed the title generating codegen for old or upcoming chain versions ws chain version specificity Apr 10, 2023
@harrysolovay harrysolovay mentioned this issue Apr 10, 2023
Closed
@tjjfvi tjjfvi mentioned this issue Apr 21, 2023
Closed
@harrysolovay harrysolovay mentioned this issue Jun 25, 2023
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tjjfvi tjjfvi

Labels
codegen task
Projects
Capi
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@harrysolovay @tjjfvi