Suppose your TDEngine instance is down or unreachable for any reason. In that case, the schemaless client code will panic, making the client library unusable in production-like environments where the DB instance may be down for many reasons.
It is a basic Go code practice to check for returned errors to catch any abnormal behavior and these things should be carefully tested before going into production.
As the title says the Schemaless client doesn't check for WebSocket client errors before using it. It does, but only further in the code:
Suppose your TDEngine instance is down or unreachable for any reason. In that case, the schemaless client code will panic, making the client library unusable in production-like environments where the DB instance may be down for many reasons.
It is a basic Go code practice to check for returned errors to catch any abnormal behavior and these things should be carefully tested before going into production.
Thanks.