mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 21:29:08 +03:00
kemal.earthandJoshen Lim
be994a1f62
* feat: remove redundant sort by We had conflicting sort by dropdown which clashed with the individual column sorting itself. Either we do something similar to our table editor or leave it out for now. Opting to leave it out for now. * fix: alignment of download dropdown This aligns the download dropdown on the Query Performance page to look visually correct. * feat: improved query search This improves our query search in the Query Performance area. Now it does a local search through the available queries in the table. I removed it requesting the string from server for now. Simple :x q * fix: increased width of filter popover The roles filter popover is was too narrow for its contents. Increased teh size slightly. * chore: remove commented out component * chore: update placeholder for query filter * fix: leftover prop on query performance page * feat: reintroduce sql based query for search Bringing back a hybrid approach - seems to work fine but also returns items that are not in your visible queries. * feat: use debounce on search query * feat: use nuqs instead of next router for roles * Tiny optimization for debounced search to immediately run query if clearing input * Add clear search CTA * Remove client side searching * Revert changes in useIndexInvalidation --------- Co-authored-by: Joshen Lim <joshenlimek@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