Christel Westerberg
|
dd4d6b46b1
|
fix: remove dynamic rendering
|
2024-10-02 08:10:31 +02:00 |
|
Christel Westerberg
|
a3bb1ed8a4
|
fix: make my pages dynamic to opt out of full router cache
|
2024-10-02 08:10:30 +02:00 |
|
Michael Zetterberg
|
bb93d488bb
|
fix: break the switch statement for proper logs
|
2024-09-27 08:17:54 +02:00 |
|
Simon Emanuelsson
|
af850c90e7
|
feat(SW-66, SW-348): search functionality and ui
|
2024-09-24 09:47:31 +02:00 |
|
Christel Westerberg
|
e04485d896
|
debug: log out cause for user
|
2024-08-26 15:40:37 +02:00 |
|
Michael Zetterberg
|
a33a69fb58
|
fix: improve auth handling and logging
|
2024-08-22 14:07:36 +02:00 |
|
Niclas Edenvin
|
e67212bd94
|
Merged in feature/refactor-lang (pull request #387)
feat: SW-238 Avoid prop drilling of lang
Approved-by: Michael Zetterberg
|
2024-08-14 11:00:20 +00:00 |
|
Michael Zetterberg
|
bc84122a40
|
fix(SW-236): properly handle expired token in webviews
Trying out a new pattern for errors in data fetching.
Next.js is not a fan of throwing errors. Instead it recommends returning
different shapes for each state. Ref:
https://nextjs.org/docs/app/building-your-application/routing/error-handling#handling-expected-errors-from-server-components
It requires some more detailing and a bit more refactoring in non webview part,
but it is a start. This webview specific implementation should not break web.
|
2024-08-13 16:54:33 +02:00 |
|
Michael Zetterberg
|
f5108d1a8e
|
feat: improve structure and error handling
|
2024-05-20 00:51:16 +02:00 |
|
Michael Zetterberg
|
0a862ca770
|
chore(debug): auth
|
2024-05-14 16:32:17 +02:00 |
|
Michael Zetterberg
|
7093a0b2dd
|
feat(WEB-132): add middlewares, support for seamless login and improve lang based routes
|
2024-04-10 11:23:38 +02:00 |
|
Simon Emanuelsson
|
ec4da5798b
|
feat(WEB-127): add trpc to handle requests both serverside and clientside
|
2024-03-27 11:56:06 +01:00 |
|