mirror of
https://github.com/supabase/supabase.git
synced 2026-10-16 14:49:10 +03:00
Add rewriteBqLogsSqlToClickhouse: parses the user's BigQuery logs query with the polyglot SDK, rewrites it onto the OTEL logs schema on the AST (FROM logs + source filter, drop unnest joins, nested fields -> log_attributes[...] with numeric casts), and regenerates ClickHouse SQL. The banner's button now runs this directly on the editor and only falls back to the AI Assistant when it can't. Lazy-loaded so the WASM stays out of the main bundle. Co-Authored-By: Claude Opus 4.8 (1M context) <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