mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 13:19:09 +03:00
Sean Oliver
a9e705e13a
- Add detailed logging for streaming chunks, final objects, and validation errors - Update schema to accept model's natural output formats: - References as objects with table/column fields (not strings) - Relationships as either arrays or objects (model is inconsistent) - Remove strict max table limit from schema, handle truncation in code - Simplify LIMITS constants to just MAX_PROMPT_LENGTH and MAX_TABLES - Update system prompt to specify reference object format - Gracefully handle validation failures by sending usable partial data
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