mirror of
https://github.com/supabase/supabase.git
synced 2026-10-12 21:05:06 +03:00
Claude
79ebe4dcf5
Update the RLS policies step in both code and no-code workflows to mention Data API privileges. Tables need appropriate grants for the anon and authenticated roles to be accessible via the Data API and client libraries. Adds a "Manage API privileges" action linking to the hardening docs (code workflow) and the Data API settings page (no-code workflow). https://claude.ai/code/session_01DP6wmuPTzzcoW6VZ8RyLXo
Writing components
Where to create your components
- For components that declare the general structure and layout of a page:
/components/layouts/xxx
- For components that are tightly coupled to a specific interface:
/components/interfaces/xxx
- For components that are meant to be reusable across multiple pages:
/components/ui/xxx
- Note: We're gradually moving files out of the
to-be-cleanedfolder into the respective folders as we refactor
Component structure
- If a component has constants and utility methods that are tightly coupled to itself, keep them close to the component and enclose them in a folder with an
index.tsxas an entry point - Otherwise it can just be a file on its own
- For example:
-
components/ui - SampleComponentA - SampleComponentA.tsx - SampleComponentA.constants.ts - SampleComponentA.utils.ts - SampleComponentA.types.ts - index.ts - SampleComponentB.tsx
-
Template for building components
// Declare the prop types of your component
interface ComponentAProps {
sampleProp: string
}
// Name your component accordingly
const ComponentA = ({ sampleProp }: ComponentAProps) => {
return <div>ComponentA: {sampleProp}</div>
}
export default ComponentA