Nested functions.

[Digital39999]

Is there any reason why status or such don't return this so it allows for easier nesting? I mean I get that its a little useless, but I write that if block so many times that it already annoys me because it can be nicer inline with single change. I didn't want to directly create a PR, so I'm asking here.

Instead of:

if (!condition) {
    <Context>.status(401);
    return <Context>.json({ message: 'You are not authorized.' })
}

to just do:

if (!condition) return c.status(401).json({ message: 'You are not authorized.' });

[EdamAme-x]

In that case, you can use such as following code.

if (!condition) return c.json({ message: 'You are not authorized.' }, 401);

Isn't it?

[Digital39999]

I had no idea that exists, I forgot to look at the types as I just switched from express and fastify so I guess I was just used to nesting, but good to know lol, thanks.

[yusukebe]

Hi @Digital39999

Implementing a feature allowing the following syntax is not a bad idea.

c.status(401).json({ message: 'You are not authorized.' })

But, actually, we've never had trouble if status does not return a Context instance. As @EdamAme-x said, you can write like that code. So, I think we don't have to implement it now.

[Digital39999]

Yeah I agree, my bad for not seeing it before.