documented hono adapter

Author: Lars-Erik Roald

README.md

@@ -1150,7 +1150,7 @@ async function deleteRows() {
 </details>
 
 <details id="in-the-browser"><summary><strong>In the browser</strong></summary>
-<p>You can use <strong><i>Orange</i></strong> in the browser by using the adapter for Express. Instead of sending raw SQL queries from the client to the server, this approach records the method calls in the client. These method calls are then replayed at the server, ensuring a higher level of security by not exposing raw SQL on the client side.  
+<p>You can use <strong><i>Orange</i></strong> in the browser by using the adapter for Express or Hono. Instead of sending raw SQL queries from the client to the server, this approach records the method calls in the client. These method calls are then replayed at the server, ensuring a higher level of security by not exposing raw SQL on the client side.  
 Raw sql queries, raw sql filters and transactions are disabled at the http client due to security reasons.  If you would like Orange to support other web frameworks, like nestJs, fastify, etc, please let me know.</p>
 
 <sub>📄 server.ts</sub>
@@ -1197,6 +1197,32 @@ async function updateRows() {
 
 ```
 
+__Hono adapter__
+
+You can host the same HTTP endpoint with Hono by replacing `db.express()` with `db.hono()`. The browser client setup stays the same (`map.http(...)`), so you can reuse the `browser.ts` example above.
+
+<sub>📄 server.ts</sub>
+
+```ts
+import map from './map';
+import { Hono } from 'hono';
+import { cors } from 'hono/cors';
+import { serve } from '@hono/node-server';
+
+const db = map.sqlite('demo.db');
+const app = new Hono();
+
+app.use('/orange', cors());
+app.use('/orange/*', cors());
+// for demonstrational purposes, authentication middleware is not shown here.
+app.all('/orange', db.hono());
+app.all('/orange/*', db.hono());
+
+serve({ fetch: app.fetch, port: 3000 });
+```
+
+`baseFilter` and transaction hooks are also supported in `db.hono({...})`, using Hono-style request/response objects.
+
 __Interceptors and base filter__
 
 In the next setup, axios interceptors are employed on the client side to add an Authorization header of requests. Meanwhile, on the server side, an Express middleware (validateToken) is utilized to ensure the presence of the Authorization header, while a base filter is applied on the order table to filter incoming requests based on the customerId extracted from this header. This combined approach enhances security by ensuring that users can only access data relevant to their authorization level and that every request is accompanied by a token. In real-world applications, it's advisable to use a more comprehensive token system and expand error handling to manage a wider range of potential issues.