Fix support for Frameworks about laurine HOT 3 CLOSED

Hello Ed!

Sorry it took me so long - I've been unavailable for few weeks, but I am back in business!

I will make sure to figure out how to do it the best way ; While your idea is solid and definitely one way to go, I still believe it should be ready for everything by just downloading - I don't want to force some new conventions etc. I am still open to suggestions, but I should be able to code it sometime next week once I put some serious thinking about it.

For now, thanks for trying it and I will let you know here once this is done.

Sincerely
JT

from laurine.

I'm thinking if this is the best way or not, For example a solution could be to create different Localizations files per target something like:

LocalizationsApp.swift
LocalizationsKit.swift <- Framework
LocalizationsWatch.swift
LocalizationsWidget.swift

This way every target has only the set of translations required by the target but leads to duplication if the same strings are needed in different targets, on the other hand if I create a single unique Localizations file within the framework to be shared by all targets seems to be more clean, what do you think?

Best regards!

from laurine.

This will be fixed in upcoming Laurine 2.0. Please refer to #52 for any further comments.

from laurine.