Releases: paescebu/CustomKeyboardKit
Releases · paescebu/CustomKeyboardKit
1.1.1
Whats new?
- Resolved Issue #31 with the submit closure as a closure parameter not allowed to be used in an escaping context, when used with an in-place
View.customKeyboard(:)
declaration
Special thanks to @ardinh for the great example showcasing that oversight that helped us resolve this issue quickly! 🎉💪
1.1.0
Whats new?
- Resolved Issue with Fast-Appearing TextFields: Addressed a limitation where custom keyboards were not correctly applied to rapidly appearing text fields (e.g., within conditionals), causing the default keyboard to appear instead. This issue is now resolved (#25).
- Reverted Fix from Issue #2: The previous solution introduced in #2 required the use of a computed property that generated a new keyboard instance with each call, resulting in the creation of multiple new objects. The revised solution now dynamically adjusts the custom submit closures based on the currently active text field (first responder), improving both performance and functionality.
Special thanks to @fraune for the detailed bug report that helped us resolve these issues! 🎉💪
1.0.4
1.0.3
1.0.2
Minor fixes + simplifications
- Allow usage of
customKeyboard
View Modifier from any View. - This allows CustomKeyboardKit (with the help of swiftui-introspect) to automatically match/apply the closure and keyboard type to the right TextField (whether its UITextField or UITextArea doesnt matter anymore).
- This change is backwards compatible, no adjustments needed from apps to use the latest version