Inconsistent iOS Version Compatibility Checks

[ibelab]

The library contains inconsistent iOS version compatibility checks which could lead to runtime issues.

For example, in UIButton+SwiftlyUI.swift, there are implementations using iOS 15 features:

@available(iOS 15.0, *)
public extension UIButton {
    
    convenience init(configuration: () -> UIButton.Configuration) {
        self.init(configuration: configuration())
    }
    
    // ...more code...
}

However, the README claims:

✅ 企业级兼容 支持 iOS 13+，完美适配存量项目

(Enterprise-level compatibility, supports iOS 13+)

Issues

1. Some code conditionally checks for iOS 13+ but other sections require iOS 15+ without fallbacks
2. No clear documentation about which features require which iOS versions
3. No compile-time safety for users who might accidentally use iOS 15+ features on iOS 13 targets

Proposed Solution

1. Add clear version requirements in README (feature by feature)
2. Implement fallbacks for iOS 13-14 where possible
3. Create a version compatibility guide
4. Add runtime version checks to prevent crashes

This would improve the library's usability across different iOS versions.

[CoderLineChan]

Thank you for raising this issue!
The inconsistencies in iOS version checks have been addressed, and the necessary fixes have been made.
We’ve ensured better compatibility across versions as claimed, and the README has been updated accordingly.

Feel free to let us know if you spot anything else!