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

fix(vue3): align rules with Vue 2 rules #771

Merged
merged 1 commit into from
May 16, 2024
Merged

Conversation

ShGKme
Copy link
Contributor

@ShGKme ShGKme commented May 16, 2024

While I totally agree with the rules, they are much different from our rules for Vue 2 requiring having many formatting changes and even filenames between Vue 2 and Vue 3 apps. It makes diffs and backports complicated during migration period.

Signed-off-by: Grigorii K. Shartsev <me@shgk.me>
@ShGKme ShGKme added bug Something isn't working 3. to review labels May 16, 2024
@ShGKme ShGKme requested a review from susnux May 16, 2024 16:14
@ShGKme ShGKme self-assigned this May 16, 2024
@skjnldsv
Copy link
Contributor

Ok for me, no strong opinion :)

@ShGKme
Copy link
Contributor Author

ShGKme commented May 16, 2024

Ok for me, no strong opinion :)

Just for the record, I'd prefer to have those rules, but I don't want to make the difference between Vue 2 and Vue 3 huge during the migration period.

@ShGKme ShGKme merged commit 049cd90 into main May 16, 2024
9 checks passed
@ShGKme ShGKme deleted the fix/vue3-less-diff-with-vue2 branch May 16, 2024 17:20
@ShGKme ShGKme mentioned this pull request May 16, 2024
@susnux
Copy link
Contributor

susnux commented May 16, 2024

I would prefer to stick with vue guidelines here too, but makes migration harder

// Prevent conflicts with native HTML elements
'vue/multi-word-component-names': 'error',
// Allow single-word components names
'vue/multi-word-component-names': ['off'],
Copy link
Contributor

Choose a reason for hiding this comment

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

should be warning in the future, single name is really bad habit.

@ShGKme
Copy link
Contributor Author

ShGKme commented May 16, 2024

I would prefer to stick with vue guidelines here too, but makes migration harder

Alternative solution — change rules for both Vue 2 and Vue 3 (and call it a new major)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants