Updating normalizerConfig after initial render

[iamJoeTaylor]

It would be awesome if there was a way to update the config normalizerConfig specifically for my current needs devLogging after the initial render.

I'd like to expose this in an admin panel so admins can turn on logging if needed.

I'm currently using the react-query variant of Normy if it makes a difference.

[klis87]

I think we could do this. I wanted to be sure though, is it necessary for you only in development? Because like mentioned at https://github.com/klis87/normy/tree/master?tab=readme-ov-file#debugging-arrow_up , typically this is not meant to be used in production

[iamJoeTaylor]

Ah I did miss that line;

Note that this works only in development, even if you pass true, no logging will be done in production (when precisely process.env.NODE_ENV === 'production'). NODE_ENV is usually set by module bundlers like webpack for you, so probably you do not need to worry about setting NODE_ENV yourself.

I was interested in logging in Prod for Admins only. But it's not a super important feature for me.

[klis87]

In theory we could also make it configurable to allow it on production. However, I wonder if this did not spam your logs on production :) It would cause tons of logs.

Anyway, this feature was exposed mostly as curiocity, so that developers could see what is really done by Normy under the hood, and... to debug some problems if they arise etc.

[iamJoeTaylor]

Anyway, this feature was exposed mostly as curiocity, so that developers could see what is really done by Normy under the hood, and... to debug some problems if they arise etc.

These logs have extremely helpful.

In theory we could also make it configurable to allow it on production. However, I wonder if this did not spam your logs on production :) It would cause tons of logs.

No worries if you'd like to leave as is. Always a tradeoff of complexity.

[klis87]

is your setup broken in production if you use NODE_ENV !== 'production' ? If it is ok, then you would have those logs in production. And epxosing update of this config dynamically would be very easy then.