fix(layout): fix layout semantics on invite page

[icecrasher321]

Summary

fix layout semantics on invite page

Type of Change

• Bug fix

Testing

Build passes

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
sim	Building	Preview	Comment	Sep 17, 2025 4:17am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Sep 17, 2025 4:17am

[greptile-apps]

Greptile Summary

This PR addresses a layout semantics issue in the invite page by standardizing component export patterns. The changes involve converting the InviteLayout component from a named export to a default export in apps/sim/app/invite/components/layout.tsx, and updating the corresponding barrel export in apps/sim/app/invite/components/index.ts to properly re-export the default export as a named export.

The modification ensures consistency with React component export conventions while maintaining backward compatibility. The InviteLayout component, which appears to be a layout wrapper for the invitation flow, is now exported as export default function InviteLayout instead of export function InviteLayout. The index.ts file was updated to use export { default as InviteLayout } syntax to properly re-export the default export with the expected name.

This change integrates with the existing invitation system architecture, where the invite directory structure includes components for handling user invitations to workspaces. The fix ensures that imports of the InviteLayout component through the barrel export continue to work correctly without requiring changes to consuming code.

Confidence score: 5/5

• This PR is safe to merge with minimal risk
• Score reflects simple export syntax standardization with proper backward compatibility maintained
• No files require special attention as both changes are straightforward export modifications

_{2 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}