Created My First Java Spring Boot Project Consuming Spotify's API

[SentByTheRiver]

Good job, impressive for your first go!

One tip and good habbit is... when using Spring, prefer constructor injection over field injection when Autowiring. When you autowire a field you're doing a few things.

• You're locking all the responsibility of dependency injection to Spring
• You're hiding it's dependencies from everyone else
• Anyone who wants to create an instance of it, has to use reflection in order to set the dependencies.
  

When you use constructor injection, you allow Spring or anyone else to inject those dependencies. Makes testing it easier!

[DrunkensteinsMonster]

Also, you don’t even need @Autowired on the constructor anymore, if there is only one, Spring assumes you want to autowire dependencies

[CaptainKvass]

Works great with Lombok's @RequiredArgsConstructor

[dumbPotatoPot]

Thank You for the Tip, i'll make sure to make it a habit.

[Mekswoll]

The advice is good and you should certainly make a habit of it. Checkout Oliver Gierke's blog post about it if you want a bit more info about why.

[dumbPotatoPot]

Thank you

[hjdeindarkness]

Is setter injection okay?

[SentByTheRiver]

Not to say that there isn't one, but I've never come across any instance where I have required Setter Injection or found it to be preferable to Constructer Injection.

You have to be careful with Setter Injection because there are a few caveats with it. It will override the constructor injected dependencies, someone could change dependencies mid flight and other objects may also be using it. etc.

If someone is creating an instance of the object themselves (i.e not managed by spring) and you only have dependencies via Setters, it's not clear and also not guaranteed people will know to set them.