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

Improve framework detection logic and add test coverage #29

Conversation

brodienguyen
Copy link

This PR perform some changes:

  • Update logic to handle Svelte 5 dependencies with caret (^x.x.x), exact (x.x.x), and tilde (~x.x.x) versioning to prevent exceptions when using the controller generator.
  • Add test coverage for the InertiaRailsContrib::GeneratorsHelper#guess_the_default_framework method.

Before After
BrodieMFL 2024-12-07 at 00 30 10 BrodieMFL 2024-12-07 at 00 39 07

Copy link
Owner

@skryukov skryukov left a comment

Choose a reason for hiding this comment

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

Looks great, thanks @brodienguyen! Could you port this to inertia-rails instead? I'm about to drop the installation support from this gem in upcoming week 😅

@@ -15,3 +15,6 @@ docs/.vitepress/dist
docs/.vitepress/cache

Gemfile.lock

# JetBrains
.idea
Copy link
Owner

Choose a reason for hiding this comment

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

imo, IDE-specific ignores work better in the global git config. In other cases OSS projects get invaded by different IDE users 😅

Copy link
Author

@brodienguyen brodienguyen Dec 6, 2024

Choose a reason for hiding this comment

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

Haha, I keep changing work machine so I am a bit lazy to configure those global settings. Properly it's time to unwind that bad habit then.

Copy link
Author

Choose a reason for hiding this comment

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

@skryukov I ported back to inertia-rails at:

I am going to close this PR to avoid double handling.

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