-
Notifications
You must be signed in to change notification settings - Fork 866
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
Make recommended/default editor settings available to commiters #8130
Comments
I'm not sure I understand the request here. Generally I think we prefer the standard NetBeans settings. But lots of things do not follow that. We generally don't reformat existing code unless it's being edited, as it makes changes hard to review. I assume you're aware the keyboard shortcut will limit itself to the selection? |
The NB project does not have any enforced formatting. For new code we encourage formatting which is close to NB's default settings - some prefer longer lines, others wrap more often - it doesn't have to be that strict IMO. So even if we would add project specific settings for this repo, you couldn't simply hit reformat after editing without causing unrelated changes. Reformatting the whole repo would be a big disturbance for little gain. Better investment would be deprecation warning fixes for example. |
Thank you for the answer, but I still have the following problems.
It would be sufficient if one of the regular committers like Neil or Michael would simply export their settings I must say that in some places the formatting of some sources is really off, making comprehensibility a lot harder, and impairing work on bug resolution. In particular, the reformatting stuff is difficult to understand because of the lack of doc on how things (should) work (compile/parse and diffing). |
i am not sure if modules can inherit a repository wide formatter setting from the parent project. Only few modules come with their own formatter config: I am also not sure how to write all defaults into a property file, it seems to add only settings which were modified plus a few extra. Btw it is really easy to start NetBeans with default config. All you have to do is |
Thanks for the tips. Other than avoiding reformatting is there any other best practice you can advise? Is there any need for a general cleanup? Documentation is a feature seldom asked for, |
Description
When working on a bug fix, one might accidentally invoke reformatting either by global settings or the keyboard shortcut, which is engraved in my muscle memory.
This messes up the code.
Use case/motivation
Avoid extra work
My personal preferences may differ from the recommended (I like horizontal whitespace to improve readability),
so to avoid and extra work, I would like to use the project-specific settings.
Related issues
earlier pull request
Are you willing to submit a pull request?
Yes
The text was updated successfully, but these errors were encountered: