As far I understood the problem we have two possible solutions:
Either need to mark the whole enum as @available(iOS 13.0, *)
Or need to increase your deployment target to iOS 13.0
Last one is not want we want to do for this library. First one could be achieved with "Nested Enums" (At least I think so).
This is want I did in this pull request. Want do you think? Feedback highly welcome. 🤗
I think a new release of the library could help out people using Cocoapod integration and missing out on the latest commits to master...
Are there any plan on this?
As far I understood the problem we have two possible solutions:
Last one is not want we want to do for this library. First one could be achieved with "Nested Enums" (At least I think so). This is want I did in this pull request. Want do you think? Feedback highly welcome. 🤗
For info about "Nested Enums" see https://developerinsider.co/advanced-enum-enumerations-by-example-swift-programming-language/