Ideas for contributions 💡

[dargmuesli]

Hey there! This project provides a pretty solid wrapper for the Spotify Web API. Although stable, there are some things that would benefit from you contributing! 🚀

• migrate to Gradle: it seems that for some good reasons most modern projects use Gradle
• migrate to Kotlin: the hypothesis to be proven here is a reduction in boilerplate code
• general code cleanup: IDEs like IntelliJ IDEA suggest some various improvements across the codebase which should be applied
• code formatting tooling: there should be some linting to ensure consistent code formatting in all relevant files

Pick one, communicate your pick and open a PR! About a thousand stargazers would very much appreciate your work 🎉

[Selbi182]

I mean, I could do the IntelliJ IDE cleanup. Just running Inspect project for any warnings and stuff shouldn't be too difficult.

[dargmuesli]

Ok, no hurry, it's just some beautification 🎨 if anything's more urgent, do that first, it's a nice to have 😉

[Selbi182]

This might take a while...

[dargmuesli]

Those HTML / JS / TS warnings can most likely be ignored as they should occur in the automatically generated documentation. Of course it would be cool if some IDEA configuration could be added so that generated code is excluded from inspections.

[Selbi182]

#386 PR is up, though I'd ask for a second opinion. This was pretty underwhelming lol

[alerGeek]

Hey @dargmuesli ,
Maybe I will take a look at one of topic next week. Regarding the migration to gradle/kotlin - do I correctly understand, that it is about replacing maven way of building application. In this case make sense to only one of these options should be chosen?

Or are we talking about:

1. migrating software automation system from maven to gradle
2. (and) migrating application langues from java to kotlin?

[dargmuesli]

@alerGeek let's open a new comment thead for your question.
Yes, migration to Gradle should be separate from migrating the programming language.

[dargmuesli]

The main question that's needed to be answered is if Gradle has a working replacement for maven-gpg-plugin. The gpg signing has been setup by the previous maintainer for this repository and I'm not 100% sure if a simple migration is possible, but it should be.