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

incosistent with prettier cli and introducing syntaxt error. #200

Closed
rnmhdn opened this issue Aug 29, 2019 · 4 comments
Closed

incosistent with prettier cli and introducing syntaxt error. #200

rnmhdn opened this issue Aug 29, 2019 · 4 comments

Comments

@rnmhdn
Copy link

rnmhdn commented Aug 29, 2019

I have the following file and it's called test.vue

<template>
  <div>
    <span>
      {{ video.selected ? "This video is included in the charts" : "This video is not included in the charts" }}
    </span>
  </div>
</template>

I run prettier test.vue and I get:

<template>
  <div>
    <span>
      {{
        video.selected
          ? "This video is included in the charts"
          : "This video is not included in the charts"
      }}
    </span>
  </div>
</template>

But I do :Prettier in vim and I get:

<template>
  <div>
    <span>
      {{ video.selected ? "This video is included in the charts" : "This video is not
      included in the charts" }}
    </span>
  </div>
</template>

which is actually syntax error.

@mitermayer
Copy link
Member

Hi @aranmohyeddin,

Would you mind providing some information to help me debug this issue ?

From inside vim whats the output of ?

  • :PrettierCliVersion
  • :PrettierCliPath
    *:PrettierVersion

and from your command line, whats the output of prettier --version and vim --version

Thanks a lot!

@rnmhdn
Copy link
Author

rnmhdn commented Aug 30, 2019

1.16.3
/home/blah/node_modules/.bin/prettier
0.2.7
1.18.2
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 29 2019 20:38:53)

@rnmhdn
Copy link
Author

rnmhdn commented Sep 3, 2019

Please tell me if you need any other information on this.

@mitermayer
Copy link
Member

This issue has been fixed on release/1.x branch

Closing this for now

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