We want to introduce the EmailAddress(String) and the EmailAddress(String, String) constructors for replacing the fromString(Any) and the fromString(Any, Any) functions from the EmailAddress.Companionexperimental type.
class EmailAddress {
constructor(text: String)
constructor(text: String, pattern: String)
}
✅ Checklist
[ ] ✨ Add the EmailAddress(String) constructor with tests, documentation and sample, then update the unreleased changelog.
[ ] 🗑️ Deprecate the EmailAddress.Companion.fromString(Any) function with an error level for using the EmailAddress(String) constructor, then update the unreleased changelog.
[ ] ✨ Add the EmailAddress(String, String) constructor with tests, documentation and sample, then update the unreleased changelog.
[ ] 🗑️ Deprecate the EmailAddress.Companion.fromString(Any, Any) function with an error level for using the EmailAddress(String) constructor, then update the unreleased changelog.
[ ] 📝 Create an issue on GitHub for removing the EmailAddress.Companion.fromString(Any) and the EmailAddress.Companion.fromString(Any, Any) functions in the next version.
📝 Description
We want to introduce the
EmailAddress(String)and theEmailAddress(String, String)constructors for replacing thefromString(Any)and thefromString(Any, Any)functions from theEmailAddress.Companionexperimental type.✅ Checklist
EmailAddress(String)constructor with tests, documentation and sample, then update the unreleased changelog.EmailAddress.Companion.fromString(Any)function with an error level for using theEmailAddress(String)constructor, then update the unreleased changelog.EmailAddress(String, String)constructor with tests, documentation and sample, then update the unreleased changelog.EmailAddress.Companion.fromString(Any, Any)function with an error level for using theEmailAddress(String)constructor, then update the unreleased changelog.EmailAddress.Companion.fromString(Any)and theEmailAddress.Companion.fromString(Any, Any)functions in the next version.