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
2024-04-16 11:36:53 +02:00
2024-08-12 14:21:09 +02:00
2024-07-08 10:17:35 +02:00
2024-05-22 11:50:29 +02:00
2024-08-13 08:52:54 +02:00
2024-04-23 14:43:17 +02:00
2024-02-29 17:52:29 +01:00
2024-04-23 14:43:17 +02:00
2024-01-09 15:48:28 +01:00
2024-01-09 15:48:28 +01:00

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

Description
No description provided
Readme 80 MiB
Languages
TypeScript 90.3%
CSS 7.6%
JavaScript 1.9%