mirror of
https://github.com/supabase/supabase.git
synced 2026-10-11 20:35:07 +03:00
* fix(studio): use paginated buckets query for useSelectedBucket Part of the effort to migrate all buckets list queries to the paginated version. This migrates the useSelectedBucket hook, which is used on the bucket details page to fetch the bucket info. * fix(studio): flash of stale content when switching buckets There's a flash of stale content when switching between buckets in the File Explorer. This happens since the change to useSelectedBucket, because when the bucket changes, the new data is no longer available immediately. It must be awaited, and meanwhile `columns` in global storage state is stale. This commit adds a check for whether the state is stale by checking the current ID against the stored ID. --------- Co-authored-by: Ali Waseem <waseema393@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