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

False positive for conflict on model generation #956

Closed
ABruel opened this issue Nov 3, 2024 · 0 comments · Fixed by #957
Closed

False positive for conflict on model generation #956

ABruel opened this issue Nov 3, 2024 · 0 comments · Fixed by #957

Comments

@ABruel
Copy link
Contributor

ABruel commented Nov 3, 2024

Description
Creating a scaffold my_test followed by another scaffold test will end in an invalid state since the migration for the second model won't be created.

To Reproduce
$ cargo loco generate scaffold my_test p:string --api
$ cargo loco generate scaffold test o:string --api

Expected Behavior

Both should fully apply their respective injections since the migration names are similar, but not the same.

Environment:
Windows. Loco 0.12.

Additional Context
Issue being created solely for tracking. Fix already implemented, pr coming shortly.

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 a pull request may close this issue.

1 participant