Skip to content

Conversation

@rillian
Copy link

@rillian rillian commented Jul 5, 2019

Identify Vue.js Single File Component source files by their .vue
filename extension and set the filetype to html. They're a mixture
of html templates, css, and javascript. The html syntax highlighting
works well enough.

Identify Vue.js Single File Component source files by their .vue
filename extension and set the filetype to html. They're a mixture
of html templates, css, and javascript. The html syntax highlighting
works well enough.
@codecov-io
Copy link

codecov-io commented Jul 5, 2019

Codecov Report

Merging #4619 into master will increase coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4619      +/-   ##
==========================================
+ Coverage   81.33%   81.34%   +0.01%     
==========================================
  Files         111      111              
  Lines      144836   144963     +127     
==========================================
+ Hits       117799   117925     +126     
- Misses      27037    27038       +1
Impacted Files Coverage Δ
src/beval.c 82.53% <0%> (-1.54%) ⬇️
src/ui.c 68.68% <0%> (-0.98%) ⬇️
src/popupwin.c 94.53% <0%> (-0.52%) ⬇️
src/ex_cmds.c 82.28% <0%> (-0.16%) ⬇️
src/term.c 79.19% <0%> (-0.06%) ⬇️
src/os_unix.c 63.3% <0%> (-0.05%) ⬇️
src/popupmnu.c 77.15% <0%> (-0.04%) ⬇️
src/mbyte.c 66.25% <0%> (ø) ⬆️
src/evalfunc.c 89.38% <0%> (ø) ⬆️
src/gui_gtk_x11.c 57.96% <0%> (ø) ⬆️
... and 13 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f5b0e5...be716d0. Read the comment docs.

@brammool
Copy link
Contributor

brammool commented Jul 5, 2019 via email

Instead of treating .vue files as html directly, define a `vuejs`
filetype and syntax file which wraps the html syntax file. This
makes it possible to override the default highlighting.
@rillian
Copy link
Author

rillian commented Jul 8, 2019

Thanks for the quick review, @brammool. I've attempted to address your comments. Please let me know how I did. :)

@brammool
Copy link
Contributor

brammool commented Jul 9, 2019 via email

@brammool brammool closed this Jul 9, 2019
@rillian
Copy link
Author

rillian commented Jul 9, 2019

Lovely, thanks!

@UncleBill
Copy link

UncleBill commented Jul 10, 2019

Can we rename vuejs to vue instead? @chrisbra

@rillian
Copy link
Author

rillian commented Jul 10, 2019

I don't have an opinion. I thought vuejs was less likely to conflict with other projects.

@brammool
Copy link
Contributor

brammool commented Jul 13, 2019 via email

@UncleBill
Copy link

UncleBill commented Jul 15, 2019

Also: the website is vuejs.org

Maybe because of vue.org is token.

  1. .vue is a single-file-component (SFC) which contains component's template, options, life-cycle hooks, and style, it more than a js file.

  2. The most popular vim plugin for vue on Github, https://github.com/posva/vim-vue , uses vue as well.

@adriaanzon
Copy link

I would be in favour of changing it to vue. There are already some plugins in the ecosystem that provide configuration for the vue filetype, e.g.:

It would be less of a hassle if existing plugins didn't have to change to vuejs.

Over at vim-vue this issue arose: posva/vim-vue#138. If we decide to change vim-vue to use vuejs as filetype, it would break existing plugins that look for the vue filetype. So at this point I'm not really sure how to move forward with this.

@brammool
Copy link
Contributor

OK, let's call it "vue" then.

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.

5 participants