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

Something wrong in .vue SFC with v-for #57

Closed
Airkro opened this issue Feb 13, 2018 · 2 comments
Closed

Something wrong in .vue SFC with v-for #57

Airkro opened this issue Feb 13, 2018 · 2 comments

Comments

@Airkro
Copy link

Airkro commented Feb 13, 2018

In my case, it's working fine, but something wrong in .vue SFC.

// .importsortrc
// my rules: https://github.com/Airkro/import-sort-style-airkro
{
  ".js": {
    "parser": "babylon",
    "style": "airkro"
  },
  ".vue": {
    "parser": "typescript",
    "style": "airkro"
  }
}

In my rules, I prefer move css file to last line.
But in following code, it won't do that.

<template>
  <div>
    <div
      :key="a"
      v-for="a in b"
    />
  </div>
</template>

<script>
import 'style.css';

import lodash from 'lodash';
</script>

Unless i put something with : symbol after v-for.

<template>
  <div>
    <div
      :key="a"
      v-for="a in b"
      :test="1"
    />
  </div>
</template>

<script>
import lodash from 'lodash';

import 'style.css';
</script>
@Airkro
Copy link
Author

Airkro commented Feb 13, 2018

Now we know this plugin working in .vue (with typescript parser). but still have labile factor.
maybe we need another parser only handle the script tag. then we can use babylon parser in .vue

@renke
Copy link
Owner

renke commented Jun 24, 2018

Let's discuss this in #66 – Vue is not really supported currently.

@renke renke closed this as completed Jun 24, 2018
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

No branches or pull requests

2 participants