mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 21:29:08 +03:00
Charis
3afbbe5986
The cron jobs details detail will throw a client side exception while cron jobs are in running status. This is because the types that we've defined for cron job details expect both return_message and end_time to be strings, but they will be null until the cron job is finished. Fixed the types and added some defensive checks to fix the bug. Also made some minor tweaks to the table. Figured that end time and duration can also be shown for failed jobs, doesn't only have to be succeeded ones.
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