Migrate to Swift #5
Conversation
hzalaz
force-pushed
the
feature-swift-migration
branch
7 times, most recently
from
654a72a to
1fe25dc
Compare
hzalaz
force-pushed
the
feature-swift-migration
branch
from
f826a11 to
9d202b0
Compare
|
Why on earth did you move this library to Swift in a without the semver version to indicate a breaking change?! It also seems strange to not change the name of the pod. It is effectively a completely different library now. While it may be compatible with Obj-C, I don't want my app's size to quadruple because you decided to dump the Swift runtime into my app without telling me! |
|
Never mind, I see that it actually was indicated as a breaking change. Are you planning on maintaining the 0.2.x branch? |
|
@billinghamj if there are some issues I'll release the proper fixes but we are not planning to add any more features, actually the swift branch won't get a lot more since the only thing missing is signature validation and for now that's not the purpose of the library. Feel free to submit any issue you find |
No description provided.