Skip to content

Conversation

michalsnik
Copy link
Member

I think we should make it clear that this plugin changed repository and all further questions should be asked there.

This repository will soon contain completely new plugin focused on real vue.js projects' purposes.

@chrisvfritz
Copy link
Contributor

I'm not sure this is necessary, since it's only a migration from the perspective of official Vue lib maintainers. For those using this in their projects, it serves the same purpose and should support all the features it did previously, plus many more. Does that make sense?

@michalsnik
Copy link
Member Author

Hmm, technically yes. But we don't know yet if it will have all the settings it had previously. From what I understood this plugin was made for internal projects purposes thus it's in my opinion too opinionated and we should reevaluate all settings and make sure it's as generic as can be. It had only one rule so we'll probably leave it, but other settings - we'll see. If we'll leave any they'll for sure will be added in recommended configuration and not the base one. I'm on it.

@michalsnik
Copy link
Member Author

On the other hand users don't necessarily need to know what's going on with eslint-plugin-vue-libs as it has been made only for internal purposes and the one that they should be interested in is this one. And we'll probably publish v3.0.0 after integratin eslint-plugin-vue-trail anyway, so fine. Makes sense @chrisvfritz 👍

@michalsnik michalsnik closed this Jun 3, 2017
@michalsnik michalsnik deleted the migration-warning branch June 3, 2017 15:33
doug-wade pushed a commit to doug-wade/eslint-plugin-vue that referenced this pull request Apr 17, 2022
…s-not-run-in-vs-code

ASA-193: Bump version to 0.1.1 and fix logo link in Python README
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