Releases: Skyscanner/SkyFloatingLabelTextField
Releases · Skyscanner/SkyFloatingLabelTextField
v2.0.1
- Added
@discardableResult
tobecomeFirstResponder
andresignFirstResponder
. This silences Xcode warnings about unused results of those functions and brings the implementation closer to the iOS API #98. Thanks to bennokress - Disable
GCC_GENERATE_TEST_COVERAGE_FILES
andGCC_INSTRUMENT_PROGRAM_FLOW_ARCS
in release configs. This was causing rejections when submitting to Apple when the library is integrated manually or with Carthage #97. Thanks to vytautasgimbutas
v2.0.0 Swift 3 support 🎉
- Adds swift 3 support. Thanks to @DenHeadless. See #67
Fix release for CocoaPods
The tag pointed to in .podspec was not updated in the 1.3 release causing it to still point to 1.2.1 instead of 1.3. This release fixes that and correctly points the podspec to the right git tag.
V1.3 Swift 2.3 support
v1.2.1
Bugfix: title was blinking when tapping the textfield.
v1.2.0
- Added RTL language support
- Changed the behaviour of
errorMessage
, removing unnecessary business logic.- Before this change there was some "hidden" business logic around the resetting of errorMessage, namely:
- Whenever the control was selected by a user, it got cleared (becomeFirstResponder invoked)
- Whenever the text changed, it also got reset (when
textField(textField:,range:string:)
was invoked)
- After this change what's different:
- The errorMessage is no longer reset by any text or focus changes. If a developer sets this message, the error will be displayed, until this property is cleared. To implement the previous functionality, just subscribe to the
textField(textField:,range:string:)
event on the delegate - As a side effect of this, the workaround of double-invoking
textField(textField:,range:string:)
has been removed, fixing the bug raised by this Issue
- The errorMessage is no longer reset by any text or focus changes. If a developer sets this message, the error will be displayed, until this property is cleared. To implement the previous functionality, just subscribe to the
- Before this change there was some "hidden" business logic around the resetting of errorMessage, namely:
v1.1.1
- Bugfix: setting the error message via the
textField?(shouldChangeCharactersInRange:replacementString:)
method is now possible - Added example on how to use the control from Objective C
v1.1
- Changed the control to inherit from the
UITextField
class (previously the control inherited fromUIControl
) - The delegate to use with the textfield is now the
UITextFieldDelegate
(removed thedelegate:SkyFloatingLabelTextFieldDelegate
class) - Removed
placeHolderLabel
,textField
andhasText
properties fromSkyFloatingLabelTextField
class - Removed
textRectForBounds(bounds: CGRect)
andplaceholderLabelRectForBounds(bounds:CGRect)
methods fromSkyFloatingLabelTextField
- The above methods have been replaced with the
UITextfield
methodseditingRectForBounds(bounds: CGRect)
andplaceholderRectForBounds(bounds: CGRect)
onSkyFloatingLabelTextField
- Added
placeholderFont
,editingOrSelected
properties toSkyFloatingLabelTextField
class
v1.0.6
Removed the hideKeyboardWhenSelected property. This property seemed too specific. To hide the keyboard when selecting a field, an alternative workaround is to set the textField.inputView property to an empty view.
v1.0.5
- Added the hideKeyboardWhenSelected property
- Bugfix: When invoking becomeFirstResponder on a textField that was not yet visible, the keyboard did not show up.