You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I would expect is that Typhoon will merge iPhone/iPad-specific assembly list with general one. But Typhoon just ignores TyphoonInitialAssemblies config key and uses one of device-specific lists.
If there is any reason against merging, the documentation should be more explicit about that.
The text was updated successfully, but these errors were encountered:
Correct, devices-specific assemblies has higher priority.
If you need something like "merge", you can just inherit your IPhoneSpecificComponents and IPadSpecificComponents classes from DeviceIndependentComponents.
In that case each device specific assembly will have all components from the device independent assembly
I think that approach is more clear than implicit merging
Consider this config:
TyphoonInitialAssemblies
TyphoonInitialAssemblies(iPhone)
TyphoonInitialAssemblies(iPad)
What I would expect is that Typhoon will merge iPhone/iPad-specific assembly list with general one. But Typhoon just ignores TyphoonInitialAssemblies config key and uses one of device-specific lists.
If there is any reason against merging, the documentation should be more explicit about that.
The text was updated successfully, but these errors were encountered: