Skip to content
This repository has been archived by the owner on Dec 20, 2022. It is now read-only.

Define style guide for consistency in code formatting #14

Open
d-gs opened this issue Aug 23, 2019 · 1 comment
Open

Define style guide for consistency in code formatting #14

d-gs opened this issue Aug 23, 2019 · 1 comment
Assignees
Labels
Prio: Medium Medium Priority Status: Accepted Issue or PR is accepted Type: Maintenance Issue or PR is a maintenance work

Comments

@d-gs
Copy link
Member

d-gs commented Aug 23, 2019

Feature request

Style guides should be defined for consistency in the source code formatting.
This also include adding Eclipse formatting rules to import in the IDE to help developers to apply them.

Expected Behavior - What where you expecting to happen?

Developers should be able to check or automatically format their code; maintainers should have a guide to review formatting changes and ask for re-formatting in case of non-conformance.

Current Behavior - What happens?

No guidelines and Eclipse auto-formatting causes unwanted changes, which adds some clutter to the PRs to be reviewed.

Possible Solution

Provide a style guide into the guidelines and formatting files for the IDEs (Eclipse and maybe others).

Context

PRs contain some changes due to re-formatting by Eclipse, which was temporarily fixed by #12.

Notes and further information

@d-gs d-gs added Type: Maintenance Issue or PR is a maintenance work Status: Pending Issue or PR awaits response Prio: Triage Triage Priority labels Aug 23, 2019
@d-gs d-gs mentioned this issue Aug 23, 2019
9 tasks
@holzerma
Copy link
Member

we need a solutions which works for every project in this organization.
see aposin/LicenseScout#27

@holzerma holzerma added Prio: Medium Medium Priority Status: Accepted Issue or PR is accepted and removed Prio: Triage Triage Priority Status: Pending Issue or PR awaits response labels Aug 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Prio: Medium Medium Priority Status: Accepted Issue or PR is accepted Type: Maintenance Issue or PR is a maintenance work
Projects
None yet
Development

No branches or pull requests

2 participants