React, Remix, Supabase, shadcn/ui (= Tailwind + Radix UI), TypeScript, Vite

1. Fork this repo (see the gray Fork button on GitHub)
2. Clone your new repo to your computer (see the green <> Code button on GitHub)
3. Start Docker (used for Supabase)
4. Start Supabase: npx supabase start (tip: you can run the Supabase web dashboard)
5. Take note of anon key when starting Supabase. Use npx supabase status if you didn’t get this already
6. Copy .env.example to .env and update SUPABASE_ANON_KEY from step 4
7. Reset/seed the database: npx supabase db reset
8. Install NPM packages: npm install

Run the app with:

npm run dev

Go to http://localhost:3000/ and log in with:

• Email: [email protected]
• Password: henricmalmberg

We normally use Linear for issue tracking and creating branch names, but ignore this for now.

1. Create new branch for the new feature/fix: [username]/[description-of-feature] (PR title: “Description of feature”).
2. Write your amazing code.
3. Apply code linting/prettifier – npm run fix (or npm run precommit if you modified the database) – before committing code and correct any issues.
4. Create a new pull request (PR) on GitHub.
5. Tech Lead will review your pull request.

P.S. It’s ok to merge main branch into your own feature branch to solve conflicts.

Create empty, time-stamped migration file with:

npx supabase migration new [migration-name]

After migration:

1. Test migrations and seeding with npx supabase db reset
2. Update the TypeScript types from Supabase/Postgres tables with npm run gentypes

• Aim for 1) readability, then 2) minimalism/DRY:ness: “Code is read more than it is written”.
• Create functions that take an object as argument instead of multiple arguments where possible. Prefer function foo({ arg1, arg2 }) over function foo(arg1, arg2).
• Use React.FC for components.
• Use a TypeScript interface called ...Props for complex function arguments, e.g: const CategoryCard: React.FC<CategoryCardProps>
• Event handlers starts with handle, props with on: onPress={handlePressButton}.
• Organise your imports in groups: external imports, business logic, components, assets.
• Define global TypeScript types including “shortcuts” to Supabase types in global.d.ts.

• Make a Supabase/Postgres SQL view with all columns you need, e.g. view_emission_factors
• Create a file for your page/route (e.g. app/routes/my-page.tsx) with this structure:
  1. Load data: loader (Remix)
  2. Render: export default function MyPageName (React component). You can use DataTable to render the list view.
  3. Form interactions: action (Remix)

Go to http://localhost:3000/bigcorp/overview/2025/esrs/e1/e1-2/members

Currently we have statuses Owner and Contributor (member in database). We now need a third status: Reviewer.

This will require changes to both database and UI.

Submit your code as a PR. Good luck!