-
Notifications
You must be signed in to change notification settings - Fork 45
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
Compatibility check on connect #84
Comments
Hi @netcodedev, while I like your suggestion, keep in mind that surrealdb is still in beta! There was a slight hickup because of a change in the websocket protocol. I patched it first thing this week after easter and we put out the v0.6.0 release of the library Tuesday evening. Once a stable 1.0.0 release is out the protocol will stay backwards compatible until a new major release. Hope that helps! Edit: would also like to add: I don't think there is actually an endpoint to check the version of surrealdb as of now |
Hi @kearfy Anyways thank you for your work on this great project 💕 |
We will definitely keep it in mind, if a method get's created for this in the protocol we can always reconsider! |
Seems like an API for checking the version is already implemented after all, I'll get this implemented soon for a check probably between 1.0.0-beta.8 and 2.0.0 AKA; it might still break during the development before 1.0.0, but should be solid afterwards! |
Great to hear! |
Switching from beta 8 to beta 9 caused a lot of trouble which made me think that it might be nice if the library had some type of compatibility check when connecting to the server.
The text was updated successfully, but these errors were encountered: