mirror of
https://github.com/supabase/supabase.git
synced 2026-10-17 15:19:08 +03:00
492c81c9c8
* Redo cron ui to use a data table * Add component for form header * Add next run column * add cron jobs page * Load jobs from url, add runs footer, link to logs * Type issue * Fix height of tab area * Use nuqs with history * improve pgcron logs, add severity filters * Check for v1.5 to see if seconds are supported * fix cron jobs logs table name * Add type to the table * Move expression warning to own function * Fit to new layout * Types * Fix long code blocks * Revert some of the changes. * Use job name as a tab name. Other minor fixes. * Use Infinite query for the cron runs. * Revert some extra changes. Will be added to another PR. * Rename pg functions --------- Co-authored-by: Terry Sutton <saltcod@gmail.com> Co-authored-by: Jordi Enric <jordi.err@gmail.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