FormValidatorSwift v2.0.0 Release Notes
Release Date: 2017-02-06 // about 7 years ago-
💥 Breaking
- ⚡️ Updated
AlphabeticCondition
andAlphanumericCondition
to allow unicode characters by default (NumericCondition
already allowed unicode characters by default).- Updated by Aaron McTavish in Pull Request #49.
- 🔧
AlphabeticCondition
,AlphanumericCondition
,CreditCardCondition
,NumericCondition
,PasswordStrengthCondition
,PostcodeCondition
, andRangeCondition
now store their configurations in aconfiguration
property rather than as top-level properties of the condition's instance. As an example, for an instance ofAlphabeticCondition
the checkcondition.allowsWhitespace == true
would becomecondition.configuration.allowsWhitespace == true
.- Updated by Aaron McTavish in Pull Request #40 and #41.
➕ Added
- ➕ Added
Configuration
,ConfigurableCondition
,ConfigurableValidator
protocols. Updated existing conditions and validators to take advantage of new protocols.- Added by Aaron McTavish in Pull Request #40 and #41.
- ➕ Added macOS support.
- Added by Aaron McTavish in Pull Request #42.
⚡️ Updated
- 0️⃣
NumericCondition
now supports ASCII only (as opposed to allowing any Unicode numeric characters) as an option. The default remains allowing Unicode characters.- Updated by Aaron McTavish in Pull Request #41.
- The
shouldAllowViolation
property on validator controls now works as expected.- Updated by sparrowlegs in Pull Request #44.
- ⚡️ Updated