-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make markymark safe to use in extensions #71
Comments
Thanks for your input. Is it possible to be any more specific? Which parts of markymark are not safe for extensions/frameworks and what solution are you proposing? Regards, Jim |
The problem is the use of |
An alternate, less hacky, solution could be delegation, where |
Thanks for your input @mhoeller-clue, i looked into your pull-request and made #74 inspired by your approach. This pull request will allow markymark to compile in extension by using NSSelectorFromString("sharedApplication") instead using UIApplication.shared directly. Also, this pull request will allow customization of the open url behavior by providing an implementation of URLOpener My collegues will review the pull request and i will let you know as soon as i release a new version. Also, let me know what you think of this approach! |
Looks perfect! It has much deeper integration throughout the system and extends the example project too 👍 |
Just release the new version! |
Currently, when trying to use markymark via cocoapods, and linking it into a framework, we get the compiler error
'shared' is unavailable: Use view controller based solutions where appropriate instead.
. This is becauseUIApplication
cannot be used from extensions or dynamically linked frameworks.A possible solution to make markymark extension safe is outlined here: https://gist.github.com/natecook1000/151d8de423eb77fc87bf#gistcomment-1656503
The text was updated successfully, but these errors were encountered: