Christian Andolf
|
e08e960209
|
chore: add consistent type imports
|
2024-12-12 11:47:44 +01:00 |
|
Simon Emanuelsson
|
af850c90e7
|
feat(SW-66, SW-348): search functionality and ui
|
2024-09-24 09:47:31 +02:00 |
|
Simon Emanuelsson
|
61b722d9ad
|
feat: handle masked values only based on MFA
|
2024-08-26 11:06:01 +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 |
|
Simon Emanuelsson
|
d84efcbb0f
|
feat(WEB-162): final design edit profile page
|
2024-06-19 14:51:00 +02:00 |
|
Simon Emanuelsson
|
55794034c5
|
feat(WEB-169): get profile data from API
|
2024-04-18 13:53:49 +02:00 |
|
Simon Emanuelsson
|
9396b2c3d5
|
feat(WEB-170): edit profile view
|
2024-04-16 09:24:31 +02:00 |
|