Skip to content

Remove all Medusa-related components and references#95

Merged
jaruesink merged 2 commits into
mainfrom
codegen-bot/remove-medusa-components-1749087159
Jun 5, 2025
Merged

Remove all Medusa-related components and references#95
jaruesink merged 2 commits into
mainfrom
codegen-bot/remove-medusa-components-1749087159

Conversation

@codegen-sh
Copy link
Copy Markdown
Contributor

@codegen-sh codegen-sh Bot commented Jun 5, 2025

Summary

This PR removes all Medusa-related components and references from the LambdaCurry/forms repository, as these have been successfully migrated to the separate medusa-forms repository.

Changes Made

Removed Packages

  • packages/medusa-forms/ - Entire package containing Medusa form components

Documentation Cleanup

  • apps/docs/src/medusa-forms/ - All Storybook stories for Medusa components
  • apps/docs/package.json - Removed @lambdacurry/medusa-forms dependency
  • apps/docs/tsconfig.json - Removed Medusa-forms path mappings
  • apps/docs/vite.config.mjs - Removed Medusa-forms alias configurations
  • apps/docs/src/main.css - Removed Medusa UI imports and extensive token definitions

Dependencies

  • yarn.lock - Automatically cleaned up unused Medusa dependencies

Verification

Build Success: Both @lambdacurry/forms and @lambdacurry/forms-docs packages build successfully
No Broken References: All Medusa imports and references have been removed
Components Package Intact: The remaining components package is unaffected

Files Removed

  • 38 files deleted, 7,887 lines removed
  • All controlled form components that wrapped @medusajs/ui
  • All related Storybook documentation and examples

The forms repository now focuses solely on the core components package, with all Medusa functionality cleanly separated into its dedicated repository.


💻 View my workAbout Codegen

@bolt-new-by-stackblitz
Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 5, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

@jaruesink jaruesink marked this pull request as ready for review June 5, 2025 05:14
@jaruesink
Copy link
Copy Markdown
Contributor

jaruesink commented Jun 5, 2025

@codegen-sh please resolve the conflicts

Will do! Resolving the conflicts now ⚡

💻 View my work

- Removed packages/medusa-forms/ package entirely
- Removed apps/docs/src/medusa-forms/ Storybook stories
- Updated apps/docs/package.json to remove @lambdacurry/medusa-forms dependency
- Cleaned up TypeScript path mappings in apps/docs/tsconfig.json
- Removed Medusa aliases from apps/docs/vite.config.mjs
- Simplified apps/docs/src/main.css to remove Medusa UI imports and tokens
- Updated yarn.lock to remove unused Medusa dependencies

All Medusa components have been successfully migrated to the separate medusa-forms repository.
@codegen-sh codegen-sh Bot force-pushed the codegen-bot/remove-medusa-components-1749087159 branch from 8187304 to 52bc10d Compare June 5, 2025 05:16
@codegen-sh
Copy link
Copy Markdown
Contributor Author

codegen-sh Bot commented Jun 5, 2025

Conflicts resolved!

I've successfully rebased the PR branch onto the latest main and resolved all merge conflicts. The conflicts were in the packages/medusa-forms/package.json file, which was expected since we're removing the entire medusa-forms package.

🔄 View Updated PR #95 🔄

What was resolved:

  • Rebased branch onto latest main (868f327)
  • Resolved conflicts in packages/medusa-forms/package.json by removing the file (as intended)
  • Build verified - both packages still build successfully after conflict resolution

The PR is now up-to-date and ready for review! 🎯

💻 View my work • React 👍 or 👎

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 5, 2025

📝 Storybook Preview: View Storybook

This preview will be updated automatically when you push new changes to this PR.

Note: The preview will be available after the workflow completes and the PR is approved for deployment.

@jaruesink
Copy link
Copy Markdown
Contributor

jaruesink commented Jun 5, 2025

@codegen-sh let's review the cursor rules to make sure there are no references in their to medusa components as well

I'll review the cursor rules for Medusa references... 🔎

💻 View my work

- Removed medusa-forms-patterns.mdc and medusa-stories-patterns.mdc files
- Cleaned up Medusa references in storybook-testing.mdc
- Updated monorepo-organization.mdc to remove Medusa package structure
- Removed reference to medusa-forms-patterns.mdc in form-component-patterns.mdc

The cursor rules now focus solely on the core forms components package.
@codegen-sh
Copy link
Copy Markdown
Contributor Author

codegen-sh Bot commented Jun 5, 2025

Cursor rules cleaned up!

I've reviewed and cleaned up all Medusa references from the cursor rules:

🔄 View Updated PR #95 🔄

Cursor rules changes:

  • 🗑️ Removed medusa-forms-patterns.mdc and medusa-stories-patterns.mdc files
  • 🧹 Cleaned up Medusa references in storybook-testing.mdc
  • 📝 Updated monorepo-organization.mdc to remove Medusa package structure
  • ✂️ Removed reference to medusa-forms-patterns.mdc in form-component-patterns.mdc

The cursor rules now focus solely on the core forms components package, with no lingering Medusa references. The repository is now completely clean of Medusa-related code and configuration! 🎯

💻 View my work • React 👍 or 👎

@jaruesink jaruesink merged commit 879e7e4 into main Jun 5, 2025
5 checks passed
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.

1 participant