Files
supabase/apps/studio/components
kemal.earth cfd6af4be0 fix(studio): autoscaling marker positioning (#47958)
## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

Small UI fix to stop things bundling into each other on smaller
viewports. Autoscaling marker moves from bottom to top to preserve
structural integrity.

| Before | After |
|--------|--------|
| <img width="698" height="246" alt="Screenshot 2026-07-15 at 11 28 07"
src="https://github.com/user-attachments/assets/9bbb1bb1-a361-4658-9757-30e012098d0c"
/> | <img width="687" height="252" alt="Screenshot 2026-07-15 at 11 28
15"
src="https://github.com/user-attachments/assets/ca6b6c0a-b511-4136-835f-4321a30765b8"
/> |



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Bug Fixes**
* Fixed the Autoscaling tooltip placement on the disk space bar so it
consistently appears in the correct spot.
* Updated the tooltip trigger to use an info icon with a static
positioned tooltip, removing the previous animated trigger behavior
while preserving existing tooltip content and visibility rules.
* Improved tooltip/marker positioning accuracy by recalculating the
horizontal placement from the independently-rounded usage segments to
prevent drift.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-07-15 14:42:51 +01:00
..

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