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
Cleanup utils #162
Cleanup utils #162
Conversation
b2b6d91
to
4107587
Compare
Thanks for your PR! I'd also happily accept this PR, but I am wondering how you plan to combine the waterfall utils with the vane utils? As the waterfall plugin is started on the proxy server, it has no access to classes from the vane-core package (which is why they were duplicated, because I was lazy). Are you going to shadow them into the waterfall plugin? |
Ah, sorry it's not often I work with Java 😅. Is shadowing the best thing to do here? |
I feel you, the ecosystem isn't great. Shadowing definitely is an option, but don't ask me how to shadow a single file from another project :P I'm sure there are a plethora of ways to do it directly in the build.gradle, but I won't really be able to help you there. I'm not overly proficient in writing such specific gradle things. |
4107587
to
80919ee
Compare
Finally figured it out. |
Hey, I'm not too familiar with The command I'm using is: Am I doing something wrong or is the formatter just not used often? |
No you are not doing it wrong. We were previously using spotless to format the code, but using it just for formatting was discontinued upstream, which meant we had to abandon it after the switch to Java 17. Prior to spotless I used clang-format. When I'm programming nowadays I just use the autoformatter of my language server (eclipse.jdt.ls with neovim), so you can just ignore it. Next time is open those files they will get formatted. :) |
b0bbd20
to
e37a958
Compare
Thanks! |
vane.util.Util
into multiple classesresolve_skin
/resolve_uuid
Is there a preferred naming style for classes in
util
? Should they all have aUtil
suffix?