mirror of
https://github.com/supabase/supabase.git
synced 2026-10-11 12:25:05 +03:00
Charis
634bd2760f
Bug fix ## What is the current behavior? When a user deletes a project, the `useProjectDetailQuery` in `RouteValidationWrapper` returns an error (HTTP 404) because the project no longer exists. This triggers the `isErrorProject` effect, which shows a "You do not have access to this project" toast and redirects to the home page — even though the user intentionally deleted the project. ## What is the new behavior? The error's HTTP status code is checked before showing the toast. A 404 response (project not found / deleted) silently redirects without showing the misleading access-denied toast. The toast is still shown for other error codes (e.g. 403 Forbidden), where the "no access" message is accurate. ## Additional context Resolves FE-2831
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