-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Move trackset-features into library subfolder #2715
Conversation
@Be-ing can't request review directly :) There is the "Triage" role on GitHub now, which would give access to such things, are you using that? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea to file a PR before actually changing any code.
Please check the formatting of each file, especially check for long lines. Sometimes you need need to give clang-format a hint to get it right.
dee23e9
to
4f840a3
Compare
The trailing slashes prevent clang-format from wrapping that text into a big chunk, see: https://stackoverflow.com/a/34362422
1d4905f
to
bbabfad
Compare
63bf05a
to
c1a6054
Compare
I have rebased on master and presumably fixed all mentioned problems :) |
I would like to have this PR merged as there don't seem to any substantial issues left. Deferred tasks:
@Holzhaus please check if I resolved #2715 (comment) correctly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks mostly good.
694ee97
to
bd4a67d
Compare
@Holzhaus all should be fixed now - again, please check above (#2715 (comment)) if I did it correctly and resolve the comment |
return QStringLiteral("%1 (%2) %3") | ||
.arg( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does QStringLiteral actually work with .arg()
? I remember I tried that once and it didn't work...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm that it does work and also remember that it didn't previously. Maybe switching to QStringBuilder did the trick?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests are all succeeding, and I hope there is at least some testing covering the library. I changed this in so many places that it would be shocking if it wouldn't work and the tests would still succeed.
I didn't have any issues with formatting when using |
Thanks for the clarification! I assumed it would simply run clang-format. Made that more clear on the wiki: https://www.mixxx.org/wiki/doku.php/coding_guidelines#pre-commit |
I ran And no, I'm not doing a rebase. I just tried and ended up with horrible conflicts. |
No need to delay this PR further due to code style discussions. We have identified some shortcomings of clang-format for multi-line string literals that could be resolved later. |
I am sorry to stress this formatting issue that much. I think the PR got to this state, because you probably have messed around with clang format during development. Now you have three options to continue here:
|
@daschuer I am leaning towards option 3, but this WILL create conflicts with my follow-up PR that I've already started working on because this took so long, which I am not fond of either... Also, I am seeing quite a few things in there that make the code less readable... |
It's not as if I explicitly created new long lines. All the lines that got longer where solely because of clang-format. For the lines I worked on by hand I always checked the length. I think the hard-wrap should leave a little buffer (maybe at 100), because sometimes a line needs to be a little longer to stay readable. xeruf#3 (review) |
Nope, I didn't mess around. I have configured my IDE to automatically run clang-format on files I work on, if that doesn't produce the correct coding style without the pre-commit hook, it should be adjusted. There was only one option I tried, which was |
OK so go ahead. Since the clang-format commit does not change the code, the conflicts should be easy to solve. |
Alright, I hope we are finally done here 😅 |
Some merge conflicts have emerged. |
Me: Creates PR |
Fixed, was merely about imports :) |
@Holzhaus please merge, before more things appear :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thank you. And sorry for all the hassle.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Follow-up to my previous PR. The second commit is a pure refactor/reformat, no code changes. Tested with SCons & CMake.