docs

Author: mnahkies

packages/documentation/src/app/guides/server-templates/typescript-express/page.mdx

@@ -193,24 +193,26 @@ code generation tooling doesn't support something you need (see also [roadmap](/
 
 Eg: response headers are not yet supported.
 
-To account for these situations, we pass the raw express `req` and `res` objects to your handler implementations,
+To account for these situations, we pass the raw express `req`, `res` and `next` objects to your handler implementations,
 allowing you full control where its needed.
 ```typescript
-const createTodoList: CreateTodoList = async ({body}, respond, req, res) => {
+const createTodoList: CreateTodoList = async ({body}, respond, req, res, next) => {
     res.setHeader("x-ratelimit-remaining", "100")
     // ...your implementation
     return respond.with200().body({ /* ... */ })
   }
 ```
 
-It's also possible to skip response processing if needed by returning `ExpressRuntimeResponse.Skip` from your implementation.
+It's also possible to skip response processing if needed by returning `SkipResponse` from your implementation.
 This allows you take complete control of the response.
 ```typescript
-const getProfileImage: GetProfileImage = async ({body}, respond, req, res) => {
+import {SkipResponse} from '@nahkies/typescript-express-runtime/server'
+
+const getProfileImage: GetProfileImage = async ({body}, respond, req, res, next) => {
     res.setHeader("x-ratelimit-remaining", "100")
     res.status(200).send(Buffer.from([/*some binary file*/]))
 
-    return ExpressRuntimeResponse.Skip
+    return SkipResponse
   }
 ```
 

packages/documentation/src/app/guides/server-templates/typescript-koa/page.mdx

@@ -193,25 +193,27 @@ code generation tooling doesn't support something you need (see also [roadmap](/
 
 Eg: response headers are not yet supported.
 
-To account for these situations, we pass the raw koa `ctx` object to your handler implementations,
+To account for these situations, we pass the raw koa `ctx` object and `next` function to your handler implementations,
 allowing you full control where its needed.
 ```typescript
-const createTodoList: CreateTodoList = async ({body}, respond, ctx) => {
+const createTodoList: CreateTodoList = async ({body}, respond, ctx, next) => {
     ctx.set("x-ratelimit-remaining", "100")
     // ...your implementation
     return respond.with200().body({ /* ... */ })
   }
 ```
 
-It's also possible to skip response processing if needed by returning `KoaRuntimeResponse.Skip` from your implementation.
+It's also possible to skip response processing if needed by returning `SkipResponse` from your implementation.
 This allows you take complete control of the response.
 ```typescript
-const getProfileImage: GetProfileImage = async ({body}, respond, ctx) => {
+import {SkipResponse} from '@nahkies/typescript-koa-runtime/server'
+
+const getProfileImage: GetProfileImage = async ({body}, respond, ctx, next) => {
     ctx.set("x-ratelimit-remaining", "100")
     ctx.status =200
     ctx.body = Buffer.from([/*some binary file*/])
 
-    return KoaRuntimeResponse.Skip
+    return SkipResponse
   }
 ```