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
I have a project that requires me to consume all pods with Objective C. Since Swift >= 4 requires the explicit setting of the @objc attribute to expose Swift methods to Objective C I'm currently unable to use EventSource unless I maintain my own fork with the attributes added.
Would you be open to a pull request that adds the @objc attribute to the methods of EventSource? I've looked into it and the only method that won't be as simple as adding @objc is onComplete. This is due to its usage of Bool? and Int? in the function definition. For that method I would propose a new wrapper method be created called onCompleteBridged that would be exposed to Objective C and would handle unwrapping the props to Objective C compatible NSNumber?
The text was updated successfully, but these errors were encountered:
Hello,
Nicholas Fredricks
I have a project that requires me to use EventSource with Objective C, but I don’t know how to use swift. Can you give me a demo? Regarding the use of EventSource in Objective C. thank you very much my friend
I have a project that requires me to consume all pods with Objective C. Since Swift >= 4 requires the explicit setting of the @objc attribute to expose Swift methods to Objective C I'm currently unable to use EventSource unless I maintain my own fork with the attributes added.
Would you be open to a pull request that adds the @objc attribute to the methods of EventSource? I've looked into it and the only method that won't be as simple as adding @objc is onComplete. This is due to its usage of Bool? and Int? in the function definition. For that method I would propose a new wrapper method be created called onCompleteBridged that would be exposed to Objective C and would handle unwrapping the props to Objective C compatible NSNumber?
The text was updated successfully, but these errors were encountered: