Skip to content

Plugin didn't change wrong name of var #142

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

Closed
peewe opened this issue Apr 4, 2017 · 8 comments
Closed

Plugin didn't change wrong name of var #142

peewe opened this issue Apr 4, 2017 · 8 comments

Comments

@peewe
Copy link

peewe commented Apr 4, 2017

Hello , I noticed that the plugin google-java-format does not change names which contains non ASCII chars.
According to, google-java-style it should change them or warning, but it doesn't do that. How do I fix it?
Thanks and have a nice day :)

@lowasser
Copy link
Contributor

lowasser commented Apr 4, 2017

? g-j-f only makes whitespace changes at this time, and that is working as intended. The formatter couldn't possibly make reasonable decisions here when it encounters non ASCII identifiers; that really requires a human's touch.

@alexkleiman
Copy link

@lowasser Is it possible that @peewe is asking why g-j-f doesn’t replace the non-ASCII versions of characters [a-z0-9A-Z] with their ASCII equivalents.

I don't know whether this is a desired feature or not, but it does at least some like something which requires less of a human touch.

@kevinb9n
Copy link
Contributor

kevinb9n commented Apr 4, 2017 via email

@sormuras
Copy link
Contributor

sormuras commented Apr 4, 2017

GJF could emit a warning.

@kevinb9n
Copy link
Contributor

kevinb9n commented Apr 4, 2017 via email

@sormuras
Copy link
Contributor

sormuras commented Apr 4, 2017

Point taken.

@sormuras
Copy link
Contributor

sormuras commented Apr 4, 2017

Is the same reasoning applicable to not consider a validation mode described in #105 (and implemented in #106)?

@kevinb9n
Copy link
Contributor

kevinb9n commented Apr 4, 2017

No, I think validation is fine as long as people understand that it means both much more and much less than validating style correctness.

@cushon cushon closed this as completed May 19, 2017
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

6 participants