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

Naming conventions for reference #30

Open
paulvi opened this issue Aug 12, 2014 · 2 comments
Open

Naming conventions for reference #30

paulvi opened this issue Aug 12, 2014 · 2 comments

Comments

@paulvi
Copy link
Contributor

paulvi commented Aug 12, 2014

I miss naming conventions as they were displayed in previous version.

jdt_spelling-10

While editing them may-be not needed, having them as reference (to point junior developers to) would be great help

@paulvi paulvi changed the title Naming conventions Naming conventions for reference Aug 12, 2014
@stuarthendren
Copy link
Owner

ok, I could bring them back as reference. It just seem a little strange as changing them didn't seem to make much sense to me. I have also been thinking about your field naming issue #27 and that lots of people probably do use UPPER_CASE for some final fields. An option could be to select a new case
say "UPPER_CASE or lowerCamelCase" and basically pass it if either one passes the spell check. The suggestions are harder if it's wrong but I can probably figure something out.

@paulvi
Copy link
Contributor Author

paulvi commented Aug 13, 2014

The values are perfect. IMHO, Show in read-only mode would do.

paulvi pushed a commit to paulvi/jdt.spelling that referenced this issue Dec 10, 2014
stuarthendren added a commit that referenced this issue Aug 21, 2021
#30 show conventions in README
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