Update use-profile.ts

[RectiFlex]

Summary by Sourcery

New Features:

• Fetch company details along with the user profile in the useProfile hook.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the useProfile hook to improve type safety, data fetching efficiency, and error handling. It introduces TypeScript interfaces for Profile and Company data, consolidates profile and company data fetching into a single query, and refines the error handling and retry logic.

Sequence diagram for updated profile data fetching flow

sequenceDiagram
    participant Client
    participant useProfile
    participant Supabase

    Client->>useProfile: Query profile data
    useProfile->>Supabase: Get session
    alt Session invalid or no user
        Supabase-->>useProfile: Session error/No user
        useProfile->>Supabase: Sign out
        useProfile-->>Client: Throw error
    else Session valid
        Supabase-->>useProfile: Session data
        useProfile->>Supabase: Fetch profile with company (single query)
        Supabase-->>useProfile: Profile and company data
        useProfile-->>Client: Return profile data
    end

Loading

State diagram for profile query retry behavior

stateDiagram-v2
    [*] --> QueryAttempt
    QueryAttempt --> Success: Data fetched
    QueryAttempt --> AuthError: 401/403 error
    QueryAttempt --> OtherError: Other errors
    AuthError --> [*]: No retry
    OtherError --> RetryOnce: First failure
    RetryOnce --> Success: Retry succeeds
    RetryOnce --> [*]: Retry fails
    Success --> [*]

Loading

File-Level Changes

Change	Details	Files
Adds TypeScript interfaces for Profile and Company to improve type safety and code clarity.	Defined Profile interface with properties like id, subscription_status, subscription_end_date, etc. Defined Company interface with properties like id, name, created_at, etc. Used these interfaces to type the useQuery hook's return value, ensuring type safety throughout the component.	src/hooks/use-profile.ts
Combines profile and company data fetching into a single query for improved efficiency.	Used a single Supabase query with a join to fetch both profile and company data simultaneously. Removed the separate query for company data, simplifying the logic and reducing network requests.	src/hooks/use-profile.ts
Improves error handling and retry logic for better user experience and resilience.	Improved session handling to sign out users with invalid sessions and throw an error. Added more specific error messages for session expiry and other potential issues. Implemented a custom retry logic to skip retries for authentication errors (401 and 403 status codes) and retry once for other errors.	src/hooks/use-profile.ts
Minor updates and improvements for code clarity and maintainability.	Updated queryKey to use double quotes for consistency. Added more detailed logging information for debugging and monitoring. Improved comments to explain the logic and purpose of different code sections.	src/hooks/use-profile.ts

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[codeautopilot]

PR summary

This Pull Request updates the use-profile.ts file to enhance type safety and improve the logic for fetching user profiles. It introduces TypeScript interfaces for Profile and Company to ensure better type checking. The profile fetching logic is simplified by directly querying the profile and associated company details in a single query, eliminating the need for a separate company fetch. Additionally, error handling is improved by providing more descriptive error messages and adjusting retry logic to avoid retries on authentication errors.

Suggestion

Consider adding unit tests to verify the new logic and ensure that the changes work as expected, especially the error handling and retry logic. This will help maintain the reliability of the useProfile hook.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 39.95%

Have feedback or need help?
Discord
Documentation
support@codeautopilot.com

[sourcery-ai]

Hey @RectiFlex - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using more specific error types instead of 'any' in the catch blocks and retry callback. This would make the error handling more type-safe and explicit.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion (code-quality): Use block braces for ifs, whiles, etc. (use-braces)

Suggested change

	if (sessionError) logger.error("Session error:", { error: sessionError });
	if (sessionError) {

Explanation

It is recommended to always use braces and create explicit statement blocks.

Using the allowed syntax to just write a single statement can lead to very confusing
situations, especially where subsequently a developer might add another statement
while forgetting to add the braces (meaning that this wouldn't be included in the condition).

[sourcery-ai]

suggestion (code-quality): Use block braces for ifs, whiles, etc. (use-braces)

Suggested change

	if (error?.status === 401 || error?.status === 403) return false;
	if (error?.status === 401 || error?.status === 403) {

Explanation

It is recommended to always use braces and create explicit statement blocks.

Using the allowed syntax to just write a single statement can lead to very confusing
situations, especially where subsequently a developer might add another statement
while forgetting to add the braces (meaning that this wouldn't be included in the condition).