Closed valeriyvan closed 1 year ago
Thanks for this, @valeriyvan! I wonder if we should remove them altogether, given that they've been renamed for a while — we can do a major release and mention this in the upgrade notes. What do you think?
Thanks for this, @valeriyvan! I wonder if we should remove them altogether, given that they've been renamed for a while — we can do a major release and mention this in the upgrade notes. What do you think?
Hi. It doesn't matter for me remove or fix properly deprecating. You better know as maintainer. What only matters for me - make project build.
I think we can go ahead and remove them :)
Solved with #354
Thanks! Seems like we can consider cutting a new release now that we're ready for Xcode 15! Would you be interested in picking that up, @valeriyvan?
Thanks! Seems like we can consider cutting a new release now that we're ready for Xcode 15! Would you be interested in picking that up, @valeriyvan?
No. I would firstly fix bug #356. Actually I did already fix it. But it's kind of bug which is much more difficult to write tests for fix then to fix.
Gotcha, thanks for bringing it up! I'm going to take a look at that, and make sure to check with you before we cut a release!
I am using this library with pods, and I am still facing this errors in Xcode 15, I do not want to unlock the pod, and just remove those lines, I have tried with Package manager and working fine, Is there any solution for pods ? @BasThomas , @valeriyvan
No, we no longer support CocoaPods for our latest versions.
Stored properties cannot be marked unavailable with '@available'
It should be marked se
deprecated
instead ofunavailable
.