- Make wasm-bindgen dependency optional. (96ccb04)
- chore: depensendcy update (adddfc0)
- chore: updated readme (1ea65ce)
- chore: updated the node version in CI (6ff216b)
- chore(npm-pkg): fixed reported vulnerability (df6de2b)
- chore(npm-pkg): updated npm deps (9ea74b8)
- Added a test for the clone functionality. (356a343)
- Dervice clone for EmailAddress struct. (f59275a)
- Ignored intellij files. (2a9c85e)
- Removed unnecessary borrows. (ba8b3e0)
- Derive Eq, PartialEq, and Hash for EmailAddress (c643037)
- Enabled parsing local part, and domain on instantiation (92b2af9).
EmailAddress::new
(in Rust) ornew EmailAddress(...)
(in JS) throws error if either local part or domain is invalid. - Added
EmailAddress::is_valid
(in Rust), andEmailAddress.isValid()
(in JS) to simply validates a given string. This parses like theparse
method, but does not instantiates anEmailAddress
object, and returntrue
/false
instead (3988d98). - Adding unicode support RFC 6532 (5d1f60e).
- The methods
localPart()
, anddomain()
exposed to JS, has been converted to ES6 getters. This meansemail.localPart()
oremail.domain()
can simply be converted toemail.localPart
andemail.domain
respectively. - In JS, the static method
EmailAddress.new
has been converted to a constructor. Use simplynew EmailAddress(...)
to instantiateEmailAddress
. - The signature of
parse
andnew
has been changed. Instead of an optional boolean as the lat parameter, they now expect an optionalParsingOptions
instance. - The constructor function (
new
) not returnsResult<EmailAddress, String>
in Rust instead ofOption<EmailAddress>
. Semantically, this makes more sense. In JS side, the corenew
function has been wrapped with a constructor function that panics (throws error in JS). The later function is not meant to be used from Rust, and strictly for JS users.
Initial release of an RFC 5233 compliant email parser.