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
{{ message }}
This repository was archived by the owner on Sep 4, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 4, 2026. It is now read-only.
initializationOptions dictionary should be broken apart (and is strange to use from Swift) #42
The app delegate's initializationOptions dictionary contains a lot of different settings pertaining to different areas, it would be nice to delegate those responsibilities out to a controller object belonging to the "module" in question, as discussed in #41.
Also, some arrays in the dictionary, such as kAppProfileElementsListKey, rely on an NSNumber representation of enum values. This is weird to use from Swift, where you need to wrap those in something like
NSNumber(unsignedLong: enumCase.rawValue)
Issues like these could be solved more elegantly from a "module" controller.
The app delegate's
initializationOptionsdictionary contains a lot of different settings pertaining to different areas, it would be nice to delegate those responsibilities out to a controller object belonging to the "module" in question, as discussed in #41.Also, some arrays in the dictionary, such as
kAppProfileElementsListKey, rely on anNSNumberrepresentation of enum values. This is weird to use from Swift, where you need to wrap those in something likeIssues like these could be solved more elegantly from a "module" controller.