dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-12 04:45:08 +03:00

Files

T

Gildas Garcia 753638caf4 fix: storage explorer column infinite loading loads the wrong column (#44275 )

## Problem

When scrolling down in a column that has more than 200 items to trigger
its lazy loading, while other columns are displayed and the targeted
column isn't the last one, it doesn't load its items.

Fixes #43799

## Solution

- Don't rely on the storage state for opened folders for the lazy
loading
- Add the item path information to the column and use it to define the
API request path

## How to test

- create a bucket
- create a folder and upload more than 200 items in it
- in this folder, create a sub folder and upload more than 200 items in
it (make sure its name position it _before_ the files)
- refresh the page
- without scrolling the first column, select the subfolder
- now scroll down on the first column past the last of its items and
verify it loads more items
- do the same on the sub folder column

To easily create many files to upload, use the following commands:

For root folder:
```sh
for i in {0..300}
do
    echo hello >"root_$(printf "%03d" "$i").txt"
done
```

For sub folder:
```sh
for i in {0..300}
do
    echo hello >"sub_$(printf "%03d" "$i").txt"
done
```

2026-03-27 16:55:15 +01:00

grid

fix: revert changes when the value is the same as old (#44196 )

2026-03-26 14:39:37 +08:00

interfaces

fix: storage explorer column infinite loading loads the wrong column (#44275 )

2026-03-27 16:55:15 +01:00

layouts

Connect iteration (#43949 )

2026-03-27 09:14:04 +10:00

to-be-cleaned

chore(studio): filter policies by bucket name (#40456 )

2025-11-14 17:47:16 +08:00

feat(assistant): per-endpoint reasoningEffort + model config cleanup (#43981 )

2026-03-25 11:29:23 -04:00

ui-patterns/Dialogs

chore: refactor <PreventNavigationOnUnsavedChanges> by extracting a usePreventNavigationOnUnsavedChanges hook (#43900 )

2026-03-20 09:27:20 +01:00

README.md

Final replacements of ui setNotification with toast (#21885 )

2024-03-12 12:56:56 +08:00

README.md

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-cleaned folder 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.tsx as 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