chore(fmt)

Author: mceachen

src/shims/node_errors.h

@@ -36,8 +36,7 @@ inline void THROW_ERR_SQLITE_ERROR(Napi::Env env,
                                    const char *message = nullptr) {
   // Check for both null and empty string - on Windows (MSVC),
   // std::exception::what() can sometimes return an empty string
-  const char *msg =
-      (message && message[0] != '\0') ? message : "SQLite error";
+  const char *msg = (message && message[0] != '\0') ? message : "SQLite error";
   Napi::Error::New(env, msg).ThrowAsJavaScriptException();
 }
 

src/sqlite_impl.cpp

@@ -586,9 +586,11 @@ Napi::Value DatabaseSync::Prepare(const Napi::CallbackInfo &info) {
     //    empty string, causing message loss.
     //
     // 2. By storing the message in the DatabaseSync instance, we can retrieve
-    //    it here and throw a proper JavaScript exception with the original text.
+    //    it here and throw a proper JavaScript exception with the original
+    //    text.
     //
-    // See also: StatementSync::InitStatement for the other half of this pattern.
+    // See also: StatementSync::InitStatement for the other half of this
+    // pattern.
     if (HasDeferredAuthorizerException()) {
       std::string deferred_msg = GetDeferredAuthorizerException();
       ClearDeferredAuthorizerException();
@@ -1495,7 +1497,8 @@ void StatementSync::InitStatement(DatabaseSync *database,
     //    empty string, causing message loss.
     //
     // 2. By storing the message in the DatabaseSync instance, the caller can
-    //    retrieve it and throw a proper JavaScript exception with the original text.
+    //    retrieve it and throw a proper JavaScript exception with the original
+    //    text.
     //
     // 3. This matches Node.js's behavior where JavaScript exceptions from
     //    authorizer callbacks propagate correctly to the caller.