Open curtisblackwell opened 7 years ago
All good thoughts. The answer to most is I either had no idea or I simply don't care. I agree some contributor guidelines are a good idea and I'm 100% behind using all the Vue and Webpack conventions. I just know my role here is a bit higher level than the code quality / consistency.
If you're willing or able to bring some of these thoughts into the code base I'll be happy to comply.
Thanks for the ideas and for the detailed points.
@tyvdh Should I fork or do you want to give me access to this repo?
@curtisblackwell It's an open source project. Are you not able to pull and create PRs? The branch/PR method would probably be my preference.
With that said I'll go ahead and invite you since I know and trust you and you've already got a decent grasp of Vue.
I can fork, but not push a new branch. Agreed on branch/PR.
It would be helpful to have contributor guidelines. I'd want to see info on getting up and running and style guides in there. Style guides could probably just point to appropriate lint configs in most cases, though. Vue has a new style guide that I think would be good to follow.
I noticed a couple things that break convention / I'm curious about:
Source (see the second green box.)
.vue
files in a Vue project.I get not wanting to put the styles in
.vue
files, I always find that to be tedious when focusing on styles, but I always find it convenient to have the JS and template in there.