Skip to content

Latest commit

 

History

History
168 lines (119 loc) · 7.9 KB

CHANGELOG.md

File metadata and controls

168 lines (119 loc) · 7.9 KB
Raw

Master

v4.0.0

  • The error message can now be placed above or below the field. #271
  • Bump build target to 9.0 #325

v.3.8.0

  • A new tag format for release has been introduced to be compatible with Swift Package Manager(SPM). The new format does not include the v prefix in tag names. This will be the case for all tags going forward, previous v prefix tags remain in place and new tags without the v prefix has been pushed for these commits too.
  • Added support for Swift Package Manager #296. Thanks to acecilia.
  • Added support for Swift 5 #290. Thanks to jessemx109.

v3.7.0

  • Added swift_versions to podspec.
  • Added support for template images. #274.

v3.6.0

  • Added support for Swift 4.2 and Xcode 10. See #239.

v3.5.2

  • Fixed crash when overriding certain properties #216. Thanks to alextov.
  • Expose errorMessage to Objective-C and Storyboard #218. Thanks to niveuseverto.

v3.5.1

  • Prevent potential crash when self.font is nil. This might cause the component to render incorrectly, but it will not crash which is preferable. See #186

v3.5.0

  • Marked isLTRLanguage with @objc so it can be set from Objective-C code #200. Thanks to behdad-keynejad
  • Added support for different colors for line, title, text when error is set #208. Thanks to InbarSletean

v3.4.1

  • Use localizedUppercase for titleFormatter by default when available. Thanks to canaksoy.

v3.4.0

  • Added support for using an image as icon. Big thanks to PedroAnibarro1.

v3.3.0

  • Added support for a disabled state of the field #177. Big thanks to kanjanaSi.

v3.2.1

  • Add support for both Swift 3 and 4 simultaneously.

v3.2.0

  • Fixed editing rect size when clear button is present to no overlap #148
  • Added titleFont as open var to set another font in titleLabel #141. Thanks to @rabenson and @rubenadlm.

v3.1.0

Improvements

  • Made isLTRLanguage open so it can actually be set by users #121.
  • Silence warnings due to M_PI being deprecated in Xcode 8.3 #116. Thanks to @z3bi.
  • Adds UIAppearance support #118. Thanks to mwfire.
  • Fix for RTL issue while editing texts #126. Thanks to @mehrdadmaskull

No Functional Change

  • Added swiftlint and cleaned up the source code to conform with it #125. Thanks to @moogle19

v3.0.0

Breaking

Change implementation of amimation callbacks to include boolean completed flag.

Before

textfield.setTitleVisible(false, animated: true) {
	// Perform callback actions
}

Now

textfield.setTitleVisible(false, animated: true) { completed in
	// Perform callback actions using completed flag
}

See #112

v2.0.1

  • Added @discardableResult to becomeFirstResponder and resignFirstResponder. 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 and GCC_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

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

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 from UIControl)
  • The delegate to use with the textfield is now the UITextFieldDelegate (removed the delegate:SkyFloatingLabelTextFieldDelegate class)
  • Removed placeHolderLabel, textField and hasText properties from SkyFloatingLabelTextField class
  • Removed textRectForBounds(bounds: CGRect) and placeholderLabelRectForBounds(bounds:CGRect) methods from SkyFloatingLabelTextField
  • The above methods have been replaced with the UITextfield methods editingRectForBounds(bounds: CGRect) and placeholderRectForBounds(bounds: CGRect) on SkyFloatingLabelTextField
  • Added placeholderFont, editingOrSelected properties to SkyFloatingLabelTextField 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.

v1.0.4

  • Updated the description of the pod

v1.0.1

  • Added support for Swift package manager

v1.0.0

  • Initial release