mirror of
https://github.com/supabase/supabase.git
synced 2026-10-11 04:15:04 +03:00
Jordi EnricandClaude Sonnet 4.6
7fc07f287b
ClickHouse rejects a bare LIMIT clause in the middle of a UNION ALL chain — it treats LIMIT as an end-of-statement marker, so the next UNION ALL token causes a parse error. Wrapping each facet SELECT in parentheses scopes the LIMIT to that branch and satisfies the parser across all ClickHouse versions. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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