Demo floating window

[fomalhautb]

---

Important

Adds DemoFloatingWindow component for development, integrated into demo layout and stack initialization, providing user actions like sign-in and account settings.

• Behavior:
  • Adds DemoFloatingWindow component in demo-floating-window.tsx, visible only in development mode.
  • Provides user actions: sign-in, sign-out, account settings.
• Integration:
  • Integrates DemoFloatingWindow into layout.tsx within the StackProvider and StackTheme.
  • Updates getUpdatedLayout() in index.ts to include DemoFloatingWindow in the layout.
• Exports:
  • Exports DemoFloatingWindow in index.ts for external use.

^{This description was created by for 98aa609. You can customize this summary. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
stack-backend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 15, 2025 4:11pm
stack-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 15, 2025 4:11pm
stack-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 15, 2025 4:11pm

[greptile-apps]

PR Summary

Added a new draggable DemoFloatingWindow component for displaying user authentication UI, with conditional rendering based on login status.

• Added /packages/template/src/components/demo-floating-window.tsx implementing drag-and-drop functionality with mouse event handling and proper cleanup
• Component displays user avatar, email, and account options when logged in, or sign in/up buttons when logged out
• Uses backdrop blur and semi-transparent background for modern UI aesthetics
• Integrated into /examples/demo/src/app/page.tsx alongside existing PageClient component
• Exports component through /packages/template/src/index.ts while maintaining platform-specific structure

_{3 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[recurseml]

✨ No issues found! Your code is sparkling clean! ✨

🗒️ View all ignored comments in this repo

• The constraint 'TokenStoreType extends string' is too restrictive. It should likely be 'TokenStoreType extends string | object' to match the condition check in line 113 where TokenStoreType is checked against {}
• Return type mismatch - the interface declares useUsers() returning ServerUser[] but the Team interface that this extends declares useUsers() returning TeamUser[]
• There is a syntax error in the super constructor call due to the ellipsis operator used incorrectly. Objects aren't being merged correctly. This syntax usage can lead to runtime errors when trying to pass the merged object to 'super()'. Verify that the intended alterations to the object occur before or outside of the super() call if needed.
• Throwing an error when no active span is found is too aggressive. The log function should gracefully fallback to console.log or another logging mechanism when there's no active span, since not all execution contexts will have an active span. This makes the code less resilient and could break functionality in non-traced environments.

📚 Relevant Docs

• Function sets backendContext with a new configuration but doesn't pass 'defaultProjectKeys'. Since defaultProjectKeys is required in the type definition and cannot be updated (throws error if tried to set), this will cause a type error.
• The schema is using array syntax for pick() which is incorrect for Yup schemas. The pick() method in Yup expects individual arguments, not an array. Should be changed to: emailConfigSchema.pick('type', 'host', 'port', 'username', 'sender_name', 'sender_email')

📚 Relevant Docs

• Creating a refresh token with current timestamp as expiration means it expires immediately. Should set a future date for token expiration.
• The 'tools' object is initialized as an empty object, even though 'tools' is presumably expected to contain tool definitions. This could cause the server capabilities to lack necessary tool configurations, thus potentially impacting functionalities that depend on certain tool setups.

📚 Relevant Docs

• 'STACK_SECRET_SERVER_KEY' is potentially being included in every request header without checking its existence again here. Although it's checked during initialization, this could lead to security issues as it's exposed in all communications where the header is logged or captured.

📚 Relevant Docs

• When adding 'use client' directive at the beginning, it doesn't check if file.text already contains the 'use client' directive. This could lead to duplicate 'use client' directives if the file already has one.

📚 Relevant Docs