feat/logger

[Paulijuz]

A form of logging is needed. I think we can log all database actions quite easily as prisma has a built in logger we can output to where we want. However, we should probably log other stuff too. And too do that we need a standardized way (a library or something) to use for logging.

[JohanHjelsethStorstad]

Change error.tsx to log error in logger

[Paulijuz]

@JohanHjelsethStorstad could you explain how you want to use the logger in error.tsx? Do you simply want to use the logger to format error messages in the console or do you want actually gather data? If the latter then the errors would somehow need to be sent back to the server.

[JohanHjelsethStorstad]

I do not know. I just Thought that it was possible to log the same error message that the client recives. Hodeverk, if its picked up in some puber way that is fine too

[Paulijuz]

I think it'll be the easiest if we simply log just on the server side, since if the client encounters an error it's almost always from the server anyway.

[JohanHjelsethStorstad]

But often when I get the 500 error page the error logged is quite next or react specific, so I am not sure were you would pick it up

[JohanHjelsethStorstad]

Oh my bad just remembered I had to change error.tsx to a client component. Then it can’t be done, but still need some way to pick those up I think

[Paulijuz]

Just so we're clear. Are we talking about logging during development, i.e. just displaying errors in a standardized way, or logging during production, i.e. storing them for data collection?

[JohanHjelsethStorstad]

In dev it does not matter as it is already on the page, but I would like to log it on production

[Paulijuz]

Ah, ok. Then probably the easiest solution is just have the logger post the error to an endpoint. Then we'll have a client side logger and a sever side logger. We'll probably also need to disclose this to users and give them an option to opt out of data collection for the sake of gdpr.