studio/cli
2
0
Fork 0
Code Issues Pull Requests Actions Packages Releases 4 Wiki Activity

chore: checkpoint before Python removal

Browse Source
This commit is contained in:
Sienna Meridian Satterwhite
2026-03-26 22:33:59 +00:00
parent 683cec9307
commit e568ddf82a
29972 changed files with 11269302 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
vendor/email_address/.cargo-checksum.json vendored Normal file
View File

@@ -0,0 +1 @@
{"files":{".cargo_vcs_info.json":"8365f4688fba3eb66334a8b1d8d6e95e2d42a000b592b355ef6324c98e878c78",".github/ISSUE_TEMPLATE/bug_report.md":"578dc22d167893ad0d881affb6e41eff1f088a87b20e8fd6b280b7f30c710e21",".github/ISSUE_TEMPLATE/feature_request.md":"aa8c9923a79c5c66fd04b18365460e1e3168f1d4afa66bee90a63ed50779165a",".github/ISSUE_TEMPLATE/spec_bug_report.md":"d75aa432b8c867336446878b3ece2869c8042cb193ab6b0a9d10e9ee0937aaa8",".github/dependabot.yml":"7b7ec82fe2dca0a362493f47e9e4e2639ed8ef80bf5e11524263aa8b8c39b63c",".github/workflows/rust.yml":"a3851610cb6c3a22dfae035d1bbefd37fd6c5ba884e811738dbb2fcfbdf2baf7",".github/workflows/security-audit.yml":"f6deeba5a2b97c0e24d17d3fc76a8063a8fad9b266235259e726ef87bd365a49",".github/workflows/typos.yml":"189ca001c78c41ef5e0c5bfc23681ab3cf083507d39b8638e28287612ea8bc0d","CODE_OF_CONDUCT.md":"d8d70df746c162c331aedf0ef86058b377b24bacb0f2de29635cd7b37e685fb5","CONTRIBUTING.md":"f90e3becb0464eacb50d4001ef0c94f94f937a6e82660ec93fd45ba7c9b2a684","Cargo.toml":"03b1bcf88de636cf1e332c365b166074e39cd58197e851326e7845bdf68796fa","Cargo.toml.orig":"6b5498efdb9ad5b3717af0649d5e09758db81347874a37d493b029a34924084d","LICENSE":"39712155836e5c10ef1b07037b606e4ad2d633e72205d162fdd7e2290aa54f15","README.md":"cbfb9fbadba8e5e1d9383ba1377577c6cc63407f6e0f2dcc394e42f68a47b2b3","pull_request_template.md":"c4847e6173d44ed3dbce978ad66abf69e280d4185b7c3c8ef94eb4bb7eaac229","src/lib.rs":"5caac172bf09e4269bd148db8ec0721ad2879f008abcf042159ec6c21157f464"},"package":"e079f19b08ca6239f47f8ba8509c11cf3ea30095831f7fed61441475edd8c449"}

6
vendor/email_address/.cargo_vcs_info.json vendored Normal file
View File

@@ -0,0 +1,6 @@
{
"git": {
"sha1": "59b64fa29a2ab701bf032a818d6ad7cf356fe024"
},
"path_in_vcs": ""
}

29
vendor/email_address/.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View File

@@ -0,0 +1,29 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''
---
## Describe the bug
A clear and concise description of what the bug is.
A clear and concise description of what you expected to happen.
## Minimal Reproducible Examples (MRE)
Please try to provide information which will help us to fix the issue faster. MREs with few dependencies are especially lovely <3.
If applicable, add logs/screenshots to help explain your problem.
**Environment (please complete the following information):**
- Platform: [e.g.`uname -a`]
- Rust [e.g.`rustic -vV`]
- Cargo [e.g.`cargo -vV`]
## Additional context
Add any other context about the problem here. For example, environment variables like `CARGO`, `RUSTUP_HOME` or `CARGO_HOME`.

28
vendor/email_address/.github/ISSUE_TEMPLATE/feature_request.md vendored Normal file
View File

@@ -0,0 +1,28 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: enhancement
assignees: ''
---
## Problem
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Include Issue links if they exist.
Minimal Reproducible Examples (MRE) with few dependencies are useful.
## Solution
A clear and concise description of what you want to happen.
## Alternatives
A clear and concise description of any alternative solutions or features you've considered.
## Additional context
Add any other context or screenshots about the feature request here.

27
vendor/email_address/.github/ISSUE_TEMPLATE/spec_bug_report.md vendored Normal file
View File

@@ -0,0 +1,27 @@
---
name: Specification Non-conformance report
about: Report an error in our implementation
title: ''
labels: specification
assignees: ''
---
## Describe the bug
A clear and concise description of what the bug is.
Please include references to the relevant specification; for example:
> RFC 2616, section 4.3.2:
>
> > The HEAD method is identical to GET except that the server MUST NOT
> > send a message body in the response
## Minimal Reproducible Examples (MRE)
Please try to provide information which will help us to fix the issue faster. MREs with few dependencies are especially lovely <3.
## Additional context
Add any other context about the problem here. For example, any other specifications that provide additional information, or other implementations that show common behavior.

10
vendor/email_address/.github/dependabot.yml vendored Normal file
View File

@@ -0,0 +1,10 @@
version: 2
updates:
- package-ecosystem: cargo
directory: "/"
schedule:
interval: daily
time: "13:00"
open-pull-requests-limit: 10
reviewers:
- johnstonskj

273
vendor/email_address/.github/workflows/rust.yml vendored Normal file
View File

@@ -0,0 +1,273 @@
name: Rust
on:
pull_request:
paths:
- '**'
- '!/*.md'
- '!/*.org'
- "!/LICENSE"
push:
branches:
- main
paths:
- '**'
- '!/*.md'
- '!/*.org'
- "!/LICENSE"
schedule:
- cron: '12 12 12 * *'
jobs:
publish:
name: Publish (dry-run)
needs: [test, docs]
strategy:
matrix:
package:
- email_address
continue-on-error: true
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: stable
profile: minimal
override: true
- uses: Swatinem/rust-cache@v2
- name: Check publish
uses: actions-rs/cargo@v1
with:
command: publish
args: --package ${{ matrix.package}} --dry-run
check_tests:
name: Check for test types
runs-on: ubuntu-latest
outputs:
has_benchmarks: ${{ steps.check_benchmarks.outputs.has_benchmarks }}
has_examples: ${{ steps.check_examples.outputs.has_examples }}
steps:
- name: Check for benchmarks
id: check_benchmarks
run: test -d benchmarks && echo "has_benchmarks=1" || echo "has_benchmarks=" >> $GITHUB_OUTPUT
shell: bash
- name: Check for examples
id: check_examples
run: test -d examples && echo "has_examples=1" || echo "has_examples=" >> $GITHUB_OUTPUT
shell: bash
test:
name: Test
needs: [rustfmt, clippy]
strategy:
matrix:
os: ["ubuntu-latest", "windows-latest", "macos-latest"]
rust: ["stable", "beta", "nightly"]
test-features: ["", "--all-features", "--no-default-features"]
continue-on-error: ${{ matrix.rust != 'stable' }}
runs-on: ${{ matrix.os }}
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: ${{ matrix.rust }}
profile: minimal
override: true
- uses: Swatinem/rust-cache@v2
- name: Build
uses: actions-rs/cargo@v1
with:
command: build
args: --workspace ${{ matrix.test-features }}
- name: Test
uses: actions-rs/cargo@v1
with:
command: test
args: --workspace ${{ matrix.test-features }}
benchmarks:
name: Benchmarks
needs: [rustfmt, clippy, check_tests]
if: needs.check_tests.outputs.has_benchmarks
strategy:
matrix:
os: ["ubuntu-latest", "windows-latest", "macos-latest"]
rust: ["stable"]
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: ${{ matrix.rust }}
profile: minimal
override: true
- uses: Swatinem/rust-cache@v2
- name: Run benchmarks with all features
uses: actions-rs/cargo@v1
with:
command: test
args: --workspace --benches --all-features --no-fail-fast
examples:
name: Examples
needs: [rustfmt, clippy, check_tests]
if: needs.check_tests.outputs.has_examples
runs-on: ubuntu-latest
strategy:
matrix:
os: ["ubuntu-latest", "windows-latest", "macos-latest"]
rust: ["stable"]
steps:
- name: Checkout repository
uses: actions/checkout@v2
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: ${{ matrix.rust }}
profile: minimal
override: true
- uses: Swatinem/rust-cache@v2
- name: Run examples with all features
uses: actions-rs/cargo@v1
with:
command: test
args: --workspace --examples --all-features --no-fail-fast
coverage:
name: Code Coverage
needs: test
runs-on: ubuntu-latest
strategy:
matrix:
os: ["ubuntu-latest", "windows-latest", "macos-latest"]
rust: ["stable"]
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: ${{ matrix.rust }}
override: true
- name: Run cargo-tarpaulin
uses: actions-rs/tarpaulin@v0.1
with:
version: 0.22.0
args: --all-features -- --test-threads 1
- name: Upload to codecov.io
uses: codecov/codecov-action@v1.0.2
with:
token: ${{secrets.CODECOV_TOKEN}}
- name: Archive code coverage results
uses: actions/upload-artifact@v1
with:
name: code-coverage-report
path: cobertura.xml
docs:
name: Document generation
needs: [rustfmt, clippy]
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: stable
profile: minimal
override: true
- uses: Swatinem/rust-cache@v2
- name: Generate documentation
uses: actions-rs/cargo@v1
env:
RUSTDOCFLAGS: -D warnings
with:
command: doc
args: --workspace --all-features --no-deps
rustfmt:
name: rustfmt
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: stable
profile: minimal
override: true
components: rustfmt
- uses: Swatinem/rust-cache@v2
- name: Check formatting
uses: actions-rs/cargo@v1
with:
command: fmt
args: --all -- --check
clippy:
name: clippy
runs-on: ubuntu-latest
permissions:
checks: write
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: stable
profile: minimal
override: true
components: clippy
- uses: Swatinem/rust-cache@v2
- uses: actions-rs/clippy-check@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
args: --workspace --no-deps --all-features --all-targets -- -D warnings

36
vendor/email_address/.github/workflows/security-audit.yml vendored Normal file
View File

@@ -0,0 +1,36 @@
name: Security audit
on:
push:
paths:
- '**/Cargo.toml'
- '**/Cargo.lock'
pull_request:
paths:
- '**/Cargo.toml'
- '**/Cargo.lock'
schedule:
- cron: '12 12 12 * *'
jobs:
security_audit:
runs-on: ubuntu-latest
permissions:
checks: write
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Install Rust
uses: actions-rs/toolchain@v1
with:
toolchain: stable
profile: minimal
override: true
- uses: actions-rs/audit-check@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}

13
vendor/email_address/.github/workflows/typos.yml vendored Normal file
View File

@@ -0,0 +1,13 @@
name: Spelling
on: [pull_request]
jobs:
spelling:
name: Spell Check with Typos
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v2
- name: Spell check repository
uses: crate-ci/typos@master

128
vendor/email_address/CODE_OF_CONDUCT.md vendored Normal file
View File

@@ -0,0 +1,128 @@
# Contributor Covenant Code of Conduct
## Our Pledge
We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity
and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.
## Our Standards
Examples of behavior that contributes to a positive environment for our
community include:
* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
overall community
Examples of unacceptable behavior include:
* The use of sexualized language or imagery, and sexual attention or
advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
## Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.
Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.
## Scope
This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
johnstonskj@gmail.com.
All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the
reporter of any incident.
## Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:
### 1. Correction
**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.
**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.
### 2. Warning
**Community Impact**: A violation through a single incident or series
of actions.
**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or
permanent ban.
### 3. Temporary Ban
**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.
**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.
### 4. Permanent Ban
**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.
**Consequence**: A permanent ban from any sort of public interaction within
the community.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https://github.com/mozilla/diversity).
[homepage]: https://www.contributor-covenant.org
For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.

91
vendor/email_address/CONTRIBUTING.md vendored Normal file
View File

@@ -0,0 +1,91 @@
# How to contribute
I'm really glad you're reading this, because we need volunteer developers to
help this project continue to grow and improve.
1. file [bugs](../../issues/new?assignees=&labels=bug&template=bug_report.md) and [enhancement requests](../../issues/new?assignees=&labels=enhancement&template=feature_request.md)
2. review the project documentation know if you find are issues, or missing
content, there
3. Fix or Add something and send us a pull request; you may like to pick up one
of the issues marked [help wanted](../../labels/help%20wanted) or [good first issue](../../labels/good%20first%20issue) as an introduction.
Alternatively, [documentation](../../labels/documentation) issues can be a great way to understand the
project and help improve the developer experience.
## Submitting changes
We love pull requests from everyone. By participating in this project, you agree
to abide by our [code of conduct](./CODE_OF_CONDUCT.md), and [License](./LICENSE).
Fork, then clone the repo:
```
git clone git@github.com:johnstonskj/{{repository-name}}.git
```
Ensure you have a good Rust install, usually managed by [Rustup](https://rustup.rs/).
You can ensure the latest tools with the following:
```
rustup update
```
Make sure the tests pass:
```
cargo test --package {{package-name}} --no-fail-fast -- --exact
cargo test --package {{package-name}} --no-fail-fast --all-features -- --exact
cargo test --package {{package-name}} --no-fail-fast --no-default-features -- --exact
```
Make your change. Add tests, and documentation, for your change. For tests
please add a comment of the form:
```rust
#[test]
// Regression test: GitHub issue #11
// or
// Feature test: GitHub PR: #15
fn test_something() { }
```
Ensure not only that tests pass, but the following all run successfully.
```
cargo doc --all-features --no-deps
cargo fmt
cargo clippy
```
If you have made any changes to `Cargo.toml`, also check:
```
cargo outdated --depth 1
cargo audit
```
Push to your fork and [submit a pull request](../../compare/) using our [template](./pull_request_template.md).
At this point you're waiting on us. We like to at least comment on pull requests
within three business days (and, typically, one business day). We may suggest
some changes or improvements or alternatives.
Some things that will increase the chance that your pull request is accepted:
* Write unit tests.
* Write API documentation.
* Write a [good commit message](https://cbea.ms/git-commit/https://cbea.ms/git-commit/).
## Coding conventions
The primary tool for coding conventions is rustfmt, and specifically `cargo fmt`
is a part of the build process and will cause Actions to fail.
DO NOT create or update any existing `rustfmt.toml` file to change the default
formatting rules.
DO NOT alter any `warn` or `deny` library attributes.
DO NOT add any `feature` attributes that would prohibit building on the stable
channel. In some cases new crate-level features can be used to introduce an
unstable feature dependency but these MUST be clearly documented and optional.

39
vendor/email_address/Cargo.toml vendored Normal file
View File

@@ -0,0 +1,39 @@
# THIS FILE IS AUTOMATICALLY GENERATED BY CARGO
#
# When uploading crates to the registry Cargo will automatically
# "normalize" Cargo.toml files for maximal compatibility
# with all versions of Cargo and also rewrite `path` dependencies
# to registry (e.g., crates.io) dependencies.
#
# If you are reading this file be aware that the original Cargo.toml
# will likely look very different (and much more reasonable).
# See Cargo.toml.orig for the original contents.
[package]
edition = "2018"
name = "email_address"
version = "0.2.9"
authors = ["Simon Johnston <johnstonskj@gmail.com>"]
publish = true
description = "A Rust crate providing an implementation of an RFC-compliant `EmailAddress` newtype. "
documentation = "https://docs.rs/email_address/"
readme = "README.md"
license = "MIT"
repository = "https://github.com/johnstonskj/rust-email_address.git"
[package.metadata.docs.rs]
targets = ["x86_64-unknown-linux-gnu"]
[dependencies.serde]
version = "1.0"
optional = true
[dev-dependencies.claims]
version = "0.7.1"
[dev-dependencies.serde_assert]
version = "0.8.0"
[features]
default = ["serde_support"]
serde_support = ["serde"]

21
vendor/email_address/LICENSE vendored Normal file
View File

@@ -0,0 +1,21 @@
MIT License
Copyright (c) 2019 Simon Johnston
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

138
vendor/email_address/README.md vendored Normal file
View File

@@ -0,0 +1,138 @@
# Crate email_address
A Rust crate providing an implementation of an RFC-compliant `EmailAddress` newtype.
![MIT License](https://img.shields.io/badge/license-mit-118811.svg)
![Minimum Rust Version](https://img.shields.io/badge/Min%20Rust-1.40-green.svg)
[![crates.io](https://img.shields.io/crates/v/email_address.svg)](https://crates.io/crates/email_address)
[![docs.rs](https://docs.rs/email_address/badge.svg)](https://docs.rs/email_address)
![Build](https://github.com/johnstonskj/rust-email_address/workflows/Rust/badge.svg)
![Audit](https://github.com/johnstonskj/rust-email_address/workflows/Security%20audit/badge.svg)
[![GitHub stars](https://img.shields.io/github/stars/johnstonskj/rust-email_address.svg)](https://github.com/johnstonskj/rust-email_address/stargazers)
Primarily for validation, the `EmailAddress` type is constructed with
`FromStr::from_str` which will raise any parsing errors. Prior to constructions
the functions `is_valid`, `is_valid_local_part`, and `is_valid_domain` may also be
used to test for validity without constructing an instance.
## Status
Currently, it supports all the RFC ASCII and UTF-8 character set rules as well
as quoted and unquoted local parts but does not yet support all the productions
required for SMTP headers; folding whitespace, comments, etc.
## Example
```rust
use email_address::*;
assert!(EmailAddress::is_valid("user.name+tag+sorting@example.com"));
assert_eq!(
EmailAddress::from_str("Abc.example.com"),
Error::MissingSeparator.into()
);
```
## Specifications
1. RFC 1123: [_Requirements for Internet Hosts -- Application and Support_](https://tools.ietf.org/html/rfc1123),
IETF,Oct 1989.
1. RFC 3629: [_UTF-8, a transformation format of ISO 10646_](https://tools.ietf.org/html/rfc3629),
IETF, Nov 2003.
1. RFC 3696: [_Application Techniques for Checking and Transformation of
Names_](https://tools.ietf.org/html/rfc3696), IETF, Feb 2004.
1. RFC 4291 [_IP Version 6 Addressing Architecture_](https://tools.ietf.org/html/rfc4291),
IETF, Feb 2006.
1. RFC 5234: [_Augmented BNF for Syntax Specifications: ABNF_](https://tools.ietf.org/html/rfc5234),
IETF, Jan 2008.
1. RFC 5321: [_Simple Mail Transfer Protocol_](https://tools.ietf.org/html/rfc5321),
IETF, Oct 2008.
1. RFC 5322: [_Internet Message Format_](https://tools.ietf.org/html/rfc5322), I
ETF, Oct 2008.
1. RFC 5890: [_Internationalized Domain Names for Applications (IDNA): Definitions
and Document Framework_](https://tools.ietf.org/html/rfc5890), IETF, Aug 2010.
1. RFC 6531: [_SMTP Extension for Internationalized Email_](https://tools.ietf.org/html/rfc6531),
IETF, Feb 2012
1. RFC 6532: [_Internationalized Email Headers_](https://tools.ietf.org/html/rfc6532),
IETF, Feb 2012.
## Changes
### Version 0.2.9
* Fixed bug [#21](https://github.com/johnstonskj/rust-email_address/issues/21): Invalid Unicode characters accepted.
### Version 0.2.8
* Fixed bug [#29](https://github.com/johnstonskj/rust-email_address/issues/29): Put back implementation of `Eq`.
### Version 0.2.7
* Feature: added builder functions to the `Option` type.
* Documentation: added examples to the `Option` type documentation.
### Version 0.2.6
* Fix: merge issues.
### Version 0.2.5
* Feature: Pull Request #15 -- Potential enhancement to add any free-text as
display name.
* Feature: Pull Request #17 -- Check for non-alphanumeric character starting or
ending domain parts.
* Feature: Pull Request #18 -- Error with `SubDomainEmpty` when empty instead of
`InvalidCharacter`.
* Feature: Pull Request #19 -- Allow configuring minimum number of subdomains.
* Feature: Pull Request #20 -- Add option to disallow domain literals.
* Feature: Pull Request #22 -- Handle a single qoute in local part of email
Thanks to [ghandic](https://github.com/ghandic), [blaine-arcjet](https://github.com/blaine-arcjet),
[Thomasdezeeuw](https://github.com/Thomasdezeeuw).
### Version 0.2.4
* Fixed bug [#11](https://github.com/johnstonskj/rust-email_address/issues/11):
1. Add manual implementation of `PartialEq` with case insensitive comparison for
domain part.
2. Add manual implementation of `Hash`, because above.
* Change signature for `new_unchecked` to be more flexible.
* Add `as_str` helper method.
### Version 0.2.3
* Added new `EmailAddress::new_unchecked` function ([Sören Meier](https://github.com/soerenmeier)).
### Version 0.2.2
* Removed manual `Send` and `Sync` implementation, and fixed documentation bug
([Sören Meier](https://github.com/soerenmeier)).
### Version 0.2.1
* Added `From<EmailAddress>` for `String`.
* Added `AsRef<str` for `EmailAddress`.
* Added `local_part` and `domain` accessors.
* More unit tests, especially for the list above.
* Added more conditions to the warning and deny list.
* Fixed some Clippy warnings.
* Fixed a bug in encoding the mailto URI scheme.
### Version 0.2.0
* Added UTF-8 support.
* Added more test cases, fixing defects in parsing.
* Method `to_uri` now supports URI encoding the address as a part of the URI.
* Added `is_valid_local_part` and `is_valid_domain` methods.
### Version 0.1.0
* Basic type implementation and structure based on RFC 5322.
* See TODO.
## TODO
1. Support comments.
1. Support line-feed and whitespace rules.
1. Does not parse _into_ `domain-literal` values, only does surface syntax check.

38
vendor/email_address/pull_request_template.md vendored Normal file
View File

@@ -0,0 +1,38 @@
# Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
## Type of change
Please delete options that are not relevant.
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update
# How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
- [ ] Test A
- [ ] Test B
**Environment (please complete the following information):**
- Platform: [e.g.`uname -a`]
- Rust [e.g.`rustic -vV`]
- Cargo [e.g.`cargo -vV`]
# Checklist:
- [ ] My code follows the style guidelines of this project (e.g. run `cargo fmt`)
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] My changes DO NOT require unstable features without prior agreement
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged and published in downstream modules

1955
vendor/email_address/src/lib.rs vendored Normal file
View File

File diff suppressed because it is too large Load Diff

BIN
vendor/email_address/target/package/email_address-0.2.9.crate vendored Normal file
View File

Binary file not shown.

0
vendor/email_address/target/package/tmp-registry/.cargo-lock vendored Normal file
View File

BIN
vendor/email_address/target/package/tmp-registry/email_address-0.2.9.crate vendored Normal file
View File

Binary file not shown.

1
vendor/email_address/target/package/tmp-registry/index/em/ai/email_address vendored Normal file
View File

@@ -0,0 +1 @@
{"name":"email_address","vers":"0.2.9","deps":[{"name":"serde","req":"^1.0","features":[],"optional":true,"default_features":true,"target":null,"kind":"normal","registry":"https://github.com/rust-lang/crates.io-index","package":null,"public":null,"artifact":null,"bindep_target":null,"lib":false},{"name":"claims","req":"^0.7.1","features":[],"optional":false,"default_features":true,"target":null,"kind":"dev","registry":"https://github.com/rust-lang/crates.io-index","package":null,"public":null,"artifact":null,"bindep_target":null,"lib":false},{"name":"serde_assert","req":"^0.8.0","features":[],"optional":false,"default_features":true,"target":null,"kind":"dev","registry":"https://github.com/rust-lang/crates.io-index","package":null,"public":null,"artifact":null,"bindep_target":null,"lib":false}],"features":{"default":["serde_support"],"serde_support":["serde"]},"features2":null,"cksum":"7b2b8344f0e72c0b3db71f2d7a5b91933e638c024ff8674eefb618eefa84a011","yanked":null,"links":null,"rust_version":null,"v":2}