How can I implement the Custom Methods approach with Hono?

[is-jonreeves]

Given that Hono uses colons to indicate path segments as params (ie. :id), does anyone know how I can implement the custom methods approach. Example:

POST /users/{id}:activate
POST /users/{id}:deactivate

[blockchainGuru1018]

1. Use Literal :method After Param
Hono allows literal segments after a param, so you can define routes like this:

import { Hono } from 'hono'

const app = new Hono()

app.post('/users/:id:activate', (c) => {
  const id = c.req.param('id')
  return c.json({ message: `User ${id} activated` })
})

app.post('/users/:id:deactivate', (c) => {
  const id = c.req.param('id')
  return c.json({ message: `User ${id} deactivated` })
})

export default app

✅ Works because :activate is literal, not a param. Hono treats :id as a param and :activate as a fixed segment.

2. Alternative: Catch-All Param and Parse
If you have many custom actions, you can define a catch-all param and parse it:

app.post('/users/:idAction', (c) => {
  const idAction = c.req.param('idAction') // e.g. "42:activate"
  const [id, action] = idAction.split(':')
  if (action === 'activate') return c.json({ message: `User ${id} activated` })
  if (action === 'deactivate') return c.json({ message: `User ${id} deactivated` })
  return c.json({ error: 'Unknown action' }, 400)
})

✅ This is more flexible if you have many actions per resource.

3. Notes / Best Practices

• Hono does not reserve :; only the first colon in a segment indicates a param.
• Literal colons after a param work fine in path segments.
• Prefer explicit routes if actions are limited (better clarity and OpenAPI support).
• Use catch-all parsing if actions are dynamic or numerous.

💡 TL;DR:

• For small sets of actions: define literal routes /users/:id:activate.
• For many dynamic actions: use /users/:idAction and split on :.

[is-jonreeves]

✅ Works because :activate is literal, not a param. Hono treats :id as a param and :activate as a fixed segment.

This is not true

[barry166]

The earlier /users/:id:activate suggestion is the part to avoid. In Hono, :id:activate is parsed as one parameter name, not as :id plus a literal :activate.

Use an explicit regexp on the parameter instead:

app.post('/users/:id{[^:]+}:activate', (c) => {
  const id = c.req.param('id')
  return c.json({ id, action: 'activate' })
})

app.post('/users/:id{[^:]+}:deactivate', (c) => {
  const id = c.req.param('id')
  return c.json({ id, action: 'deactivate' })
})

The {[^:]+} part makes id stop before the literal colon. If you have many actions, a single route like /users/:idAction and splitting on : in the handler is simpler, but for a small fixed set the regexp route keeps the handlers explicit.