-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improve node incompatibility warnings #2283
Comments
I'm not sure if it makes sense anymore to do this now that If anything, it doesn't look like a |
Makes sense — priority decreased. |
We should keep it because things like the [graphql] API can change and break stuff. Better have a warning to be safe. |
Note
Incoming from the forum:
We do have checks in place, but we call fetchChain before the check occur.
A possible solution would be to make an additional request only for the node's version before the rest.
It requires some consideration. Also, we'd need to cache this result to avoid unnecessary requests.
The text was updated successfully, but these errors were encountered: