Translations no longer work with upgrade from `2.1.0` -> `2.1.1`

[Tandashi]

With the update from version 2.1.0 to 2.1.1 the translations stopped working and only display the first segment of the translation key which broke our production code. Our quick fix currently is explicitly use 2.1.0.

Files for a minimal example: minimal-example.zip

My assumption: With the change in implementation of LocalizationService.instance.read the translation broke IF the translation key contains dots due to the split that occurs now. However I don't see anywhere in the README.md that explicitly mentions that you shouldn't use dots to split your translation keys into segments for better structuring.

Is it intended that one shouldn't use dots to split the translation key? And if so it should probably be stated in the README.md what the best practices and pitfalls are.

[charcoast]

I also had this problem.

[digibum]

Same issue here.

[leonardogbr]

Same here.