Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add rewrites and upserts for gateway.new #2779

Merged
merged 1 commit into from
Dec 23, 2024
Merged

Conversation

chronark
Copy link
Collaborator

@chronark chronark commented Dec 23, 2024

Summary by CodeRabbit

  • New Features
    • Introduced a new onboarding route for users accessing the gateway.new domain.
    • Added a CreateApiButton component with a customizable default open state.
  • Bug Fixes
    • Enhanced workspace creation logic to ensure proper initialization based on tenant ID.
  • Chores
    • Updated middleware to include the new route for improved authentication and workspace validation.
    • Added a rewrite rule for better routing capabilities related to the gateway.new domain.

Copy link

changeset-bot bot commented Dec 23, 2024

⚠️ No Changeset found

Latest commit: e339cc9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Dec 23, 2024

📝 Walkthrough

Walkthrough

This pull request introduces enhancements to the dashboard application, focusing on a new gateway.new onboarding route and improvements to API creation functionality. The changes include adding a new page for workspace creation when users access gateway.new, updating middleware to support the new route, and modifying the Next.js configuration to handle domain-specific routing. Additionally, the CreateApiButton component receives an optional defaultOpen prop to control its initial dialog state, and the APIs overview page is updated to leverage this new functionality.

Changes

File Change Summary
apps/dashboard/app/(app)/apis/create-api-button.tsx Added Props type with defaultOpen option, updated component to manage dialog open state internally
apps/dashboard/app/(app)/apis/page.tsx Added Props type for searchParams, updated ApisOverviewPage to conditionally set defaultOpen for CreateApiButton
apps/dashboard/app/(app)/gateway-new/page.tsx New route implementation for workspace creation and onboarding
apps/dashboard/middleware.ts Added "/gateway-new" to middleware route matcher
apps/dashboard/next.config.js Added rewrite rule for gateway.new domain routing

Sequence Diagram

sequenceDiagram
    participant User
    participant Browser
    participant Middleware
    participant GatewayNewPage
    participant Database

    User->>Browser: Access gateway.new
    Browser->>Middleware: Request routing
    Middleware->>GatewayNewPage: Route request
    GatewayNewPage->>Database: Check existing workspace
    alt No workspace exists
        GatewayNewPage->>Database: Create new workspace
    end
    GatewayNewPage->>Browser: Redirect to API creation page
Loading

Possibly related PRs

Suggested Labels

Feature, Dashboard, 🕹️ oss.gg, hacktoberfest

Suggested Reviewers

  • mcstepp
  • perkinsjr
  • MichaelUnkey

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

github-actions bot commented Dec 23, 2024

Thank you for following the naming conventions for pull request titles! 🙏

Copy link

vercel bot commented Dec 23, 2024

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

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 23, 2024 7:04pm
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 23, 2024 7:04pm
play ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 23, 2024 7:04pm
www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 23, 2024 7:04pm

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
apps/dashboard/app/(app)/apis/create-api-button.tsx (1)

42-42: State initialization with defaultOpen is clear.
This ensures the dialog’s open state is controlled effectively upon component mount.

Consider adding a simple memo or callback if additional logic depends on “open” to avoid unnecessary re-renders, though not essential here.

apps/dashboard/app/(app)/gateway-new/page.tsx (2)

24-32: Consider transaction safety or upsert for concurrent requests.
If two requests arrive at nearly the same time, each not finding an existing workspace, you might create duplicates. A database-level lock or an upsert approach would help ensure exactly one workspace is created.

Example snippet (PostgreSQL-like syntax):

INSERT INTO workspaces (id, name, tenantId, betaFeatures, features)
VALUES (:id, 'Personal Workspace', :tenantId, '{}', '{}')
ON CONFLICT (tenantId) DO NOTHING;

34-34: “new=true” query param might be misleading if no new workspace was created.
If the workspace already exists, the user is still redirected to “/apis?new=true”. Consider informing the user differently when no new workspace was created.

apps/dashboard/next.config.js (1)

53-63: Path segment is ignored in rewrite.
Right now, any path under gateway.new redirects to “/gateway-new”, discarding the user’s original path. If you want to preserve or reference that path, consider adjusting the destination to “/gateway-new/:path”.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 90c5da0 and e339cc9.

📒 Files selected for processing (5)
  • apps/dashboard/app/(app)/apis/create-api-button.tsx (2 hunks)
  • apps/dashboard/app/(app)/apis/page.tsx (2 hunks)
  • apps/dashboard/app/(app)/gateway-new/page.tsx (1 hunks)
  • apps/dashboard/middleware.ts (1 hunks)
  • apps/dashboard/next.config.js (1 hunks)
🔇 Additional comments (10)
apps/dashboard/app/(app)/apis/create-api-button.tsx (4)

22-22: Good addition of useState import.
This is necessary to handle local dialog state.


30-32: Optional prop is relevant for dialog state initialization.
The new type definition clarifies usage for parent components, making the component interface more robust.


34-37: Prop merge in function signature is straightforward and clear.
Combining button attributes with the new prop ensures backward compatibility and extensibility.


62-62: Properly binding the dialog open state.
You handle the dialog’s visibility cleanly by assigning it to the local open state and the onOpenChange callback.

apps/dashboard/app/(app)/apis/page.tsx (3)

15-17: Clear type definition for incoming search parameters.
Defining the optional “new” boolean in searchParams improves readability and ensures type safety.


19-19: Props-based function signature.
This clarifies that ApisOverviewPage now depends on external search parameters, which can help future maintainers.


55-58: Conditional dialog opening.
Using the condition (apis.length === 0 || props.searchParams.new) effectively handles first-time or on-demand dialog display.

apps/dashboard/app/(app)/gateway-new/page.tsx (2)

19-22: Workspace lookup logic is correct.
Looks good. The query constraints (no deletedAt, matching tenantId) make sense to identify a single active workspace.


16-18: Handle missing tenantId more gracefully.
If getTenantId() ever returns null or undefined, the subsequent logic could fail silently. Consider validating the tenantId and possibly redirecting or throwing an error if it's not set.

apps/dashboard/middleware.ts (1)

76-76: Included “/gateway-new” in the middleware matcher.
This is consistent with the new route. The addition ensures the same auth and workspace checks apply to the new path.

@chronark chronark merged commit ad3d498 into main Dec 23, 2024
28 checks passed
@chronark chronark deleted the new-single-click branch December 23, 2024 19:06
@coderabbitai coderabbitai bot mentioned this pull request Jan 3, 2025
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants