Remove uneeded guard when ID3Tag tries to find an unknown genre

[alex-quiterio]

The guard rescue nil can now be safely removed since the original issue
is fixed by krists/id3tag#19

related with: #118

[julik]

@alex-quiterio good stuff, thanks! Can you also bump the gem version dependency for id3tag in .gemspec since you need it to be 0.10.1 or newer?

[julik]

🎉 almost! We probably should use the additional constraint though, since we do not strictly forbid 0.11 and such. See https://guides.rubygems.org/patterns/

If you want to allow use of newer backwards-compatible versions but need a specific bug fix you can use a compound requirement:

[alex-quiterio]

Interesting indeed.

I didn't know about the existence of compound requirements. So in the end, we fixed the issue with the call on nil and made sure the version number of id3tag doesn't go off the fence with 0.11.

@julik thanks very much for the tip!

minor update:

Actually, after having a closer look at the documentation for Ruby's pessimistic operator we can actually make sure that by using the combination '~> 0.10.0', '>= 0.10.1' we constraint the gem to not be bumped to the next minor version.

Although, I don't think we actually need to specify that constraint for the id3tag gem, so the ideal situation would be something like: '~> 0.10', '>= 0.10.1'.

Hope this helps to be more strict without losing the flexibility we want to keep. 🙇

[julik]

🎉 👍