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

Code styles are inconsistent #1993

Open
dariusj18 opened this issue Feb 7, 2020 · 4 comments
Open

Code styles are inconsistent #1993

dariusj18 opened this issue Feb 7, 2020 · 4 comments
Labels
💭 Suggestion Proposed ideas or changes

Comments

@dariusj18
Copy link

The projects has an .editorconfig file, however there are still commits like this 7355e94 where the code changes are confusing because the spaces were changed to tabs.

Since this is a Laravel project I would advise following PSR-12.

CircleCI or GitHub actions could be used to automate testing.

Here's an example I found with a quick search of a project implementing Github actions for php code sniffing. https://github.com/typo3-trainer-network/books/pull/38/files

@trwnh trwnh added the 💭 Suggestion Proposed ideas or changes label Feb 7, 2020
@shleeable
Copy link
Contributor

It's easy to add a github action to check against these standards.

I've just done a scan and the PR to change up to PSR-1, then PSR-12 is going to effect every file ;)
So @dansup really needs to be keen to run these code standard changes, because his code standard is obviously his preference.

@dansup
Copy link
Member

dansup commented Feb 18, 2020

Someone else contributed the .editorconfig file, we did use StyleCI at one point but it wasn't configured properly so I removed it.

I plan to tackle this in v0.12 (the big refactor), will keep this open until I fix!

@dansup dansup added this to the 0.12.0 - Polish milestone Feb 18, 2020
@shleeable shleeable mentioned this issue Feb 22, 2020
@svenluijten
Copy link
Contributor

@dansup what's the status of this? As the project has gotten more contributors, I think it's smart to tackle this now before it gets too unwieldy and it can't be changed at all (if it hasn't yet). Enabling StyleCI should be pretty minor and only affect new code that's contributed to the project, so you won't have a massive PR like #2064.

@jippi
Copy link
Contributor

jippi commented Mar 2, 2024

#4921 +#4922 was intended to fix this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💭 Suggestion Proposed ideas or changes
Projects
None yet
Development

No branches or pull requests

6 participants