Rallly is an open-source scheduling and collaboration tool designed to make organizing events and meetings easier.
TypeScript i18nextnext-authnextjspostgresqlprismareact-emailt3-stacktailwindcsstrpcturborepotypescriptzod
🔥 Remove the stale .cursorrules (#3222)
Luke Vella9bbc13a489cd
diff --git a/.cursorrules b/.cursorrulesdeleted file mode 100644index ea77d5d0e..000000000--- a/.cursorrules+++ /dev/null@@ -1,42 +0,0 @@-- Use pnpm for package management-- Use dayjs for date handling-- Use tailwindcss for styling-- Use react-query for data fetching-- Use react-hook-form for form handling-- Prefer implicit return values over explicit return values-- Use zod for form validation-- Create separate import statements for types-- All text in the UI should be translated using either the Trans component or the useTranslation hook-- Prefer composable components in the style of shadcn UI over large monolithic components-- DropdownMenuItem is a flex container with a preset gap so there is no need to add margins to the children-- Keep the props of a component as minimal as possible. Pass only the bare minimum amount of information needed to it.-- All text in the UI should be translatable.-- i18n keys are in camelCase.-- Use the <Trans> component in client components from @/i18n/client. Use the `defaults` prop to provide the default text. Example:--```tsx-import { Trans } from "@/i18n/client";--<Trans i18nKey="menu" defaults="Menu" />-```--- On the server use the `getTranslations` function from @/i18n/server to get the translations. Example:--```ts-const { t } = await getTranslations();--t("menu", { defaultValue: "Menu" });-```--- shadcn-ui components should be added to packages/ui-- Always use a composable patterns when building components-- Use `cn()` from @rallly/ui to compose classes-- Prefer using the React module APIs (e.g. React.useState) instead of standalone hooks (e.g. useState)-- Do not attempt to fix typescript issues related to missing translations. This will be handled by our tooling.-- Never manually add translations to .json files. This will be handled by our tooling.-- Add the "use client" directive to the top of any .tsx file that requires client-side javascript-- i18nKeys should describe the message in camelCase. Ex. "lastUpdated": "Last Updated"-- If the i18nKey is not intended to be reused, prefix it with the component name in camelCase-- Always use kebab-case for file names-- Prefer double quotes for strings over single quotes-- Only add comments when it is necessary to explain code that isn't self-explanatory