Easy Timezone management for Responses

[tkoehlerlg]

What is the problem this feature would solve?

Would love to have a timeZone parameter in for example set to easily set a response timezone for t.Date() transformation to string. Currently i would have to set the response object to t.String() and then format the string to a timezone myself. I saw in the elysia code that forcing a timeZone is possible in the response transformation so it would be amazing if we could use it.

What is the feature you are proposing to solve the problem?

timeZone parameter somewhere to set to change the transform behavior after t.Date()

What alternatives have you considered?

Setting the response to t.String and transforming the Date object with a timezone myself.

[kravetsone]

why u need it? Date should be in ISO format without timezones (UTC)

[SaltyAom]

You can transform a response by specify a custom schema using t.Transform

t.Transform(t.Date())
    .Decode((v) => v)
    .Encode((v) => {
        return handleTimeZoneLogicHere(v)
    })

Before Elysia send the response back to client, handleTimeZoneLogicHere will be called and use it as response.

[tkoehlerlg]

@SaltyAom I tried to replicate this but it does not work or get called at all: https://github.com/tkoehlerlg/elysia-demo

@kravetsone Building some AI tools that use my Elysia API, to get timestamps to an AI, that does not understand adding 2 hours to UTC when it's German time. I would love to respond with timezone equivalent since it's no change for programmers and makes it so much easier for LLMs to work with my API.

[tkoehlerlg]

@SaltyAom Custom Transformations do not work when aot is set false! Please checkout my demo

[tkoehlerlg]

@SaltyAom any updates here? This is not about Timezones this is about how Typebox is used.