Files

Kasper Fabricius Kristensen c384ede3b1 feat(dashboard): Setup parallel V2 routes (#6691 )

**What**
- Moves all current route definitions to `v1.tsx`
- Creates a new `v2.tsx` file for future V2 routes.
- Updates RouteProvider to serve V1 or V2 routes based on if `MEDUSA_V2` is set.

**How to use it**
When working on V2 domains you should set `MEDUSA_V2=true` in `/packages/admin-next/dashboard/.env`. We can't use the Feature Flag in the Medusa project since there are breaking changes in the `/admin/store` endpoint between the two versions, so it needs to be managed manually.

**For people implementing V2 domains**
To add a new route you should:

- Add the route component in `/v2-routes`
- Define which path will render it in `v2.tsx`.

I would prefer that we don't try to implement a lot of conditional code that will make the codebase unnecessarily complex. So if I was to implement the V2 login page, I would copy/past the v1 login route into `v2-routes`, make the required changes, eg. replace `useAdminLogin` with `useAdminCustomPost(...)`, instead of trying to force the current V1 Login page to work with both APIs.

There will hopefully be a lot of components/sections from each domain that is re-usable between versions. As an example if you are working on the Product details page for V2 you might want to reuse the `product-general-section.tsx` file, as it works without having to make any modifications. In that case I propose that we create a `modules/product` folder and move the component in there which we can them import into both the v1 and v2 version of the route.

2024-03-14 18:05:44 +00:00

public

fix(dashboard): fixed some strings (#6686 )

2024-03-14 15:43:14 +00:00

scripts

feat(dashboard): add customers domain (#6093 )

2024-01-16 15:23:45 +01:00

src

feat(dashboard): Setup parallel V2 routes (#6691 )

2024-03-14 18:05:44 +00:00

.gitignore

…

index.html

…

package.json

feat(dashboard): Workflow executions (#6564 )

2024-03-09 18:46:10 +00:00

postcss.config.cjs

…

README.md

…

tailwind.config.cjs

feat(dashboard): Regions domain (#6534 )

2024-02-29 13:16:14 +00:00

tsconfig.json

…

tsconfig.node.json

…

vercel.json

add vercel config (#6018 )

2024-01-08 10:38:18 +01:00

vite.config.mts

…

README.md

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Babel for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

Configure the top-level parserOptions property like this:

export default {
  // other rules...
  parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
    project: ['./tsconfig.json', './tsconfig.node.json'],
    tsconfigRootDir: __dirname,
  },
}

Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@typescript-eslint/strict-type-checked
Optionally add plugin:@typescript-eslint/stylistic-type-checked
Install eslint-plugin-react and add plugin:react/recommended & plugin:react/jsx-runtime to the extends list