[PATCH proxmox 1/3] installer types: move email validation from proxmox-installer-common

[Dominik Csapak <d.csapak@proxmox.com>]

we want to use this not only in the installer itself but also e.g. in
PDM which can generate answer files.

Since we don't only want this when we have the api types, move the
proxmox-schema and regex dependencies from the api-types feature.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
 proxmox-installer-types/Cargo.toml    |  6 +++---
 proxmox-installer-types/src/answer.rs | 22 ++++++++++++++++++++++
 2 files changed, 25 insertions(+), 3 deletions(-)

diff --git a/proxmox-installer-types/Cargo.toml b/proxmox-installer-types/Cargo.toml
index 4526b47f..5b0b489c 100644
--- a/proxmox-installer-types/Cargo.toml
+++ b/proxmox-installer-types/Cargo.toml
@@ -15,15 +15,15 @@ rust-version.workspace = true
 anyhow.workspace = true
 serde = { workspace = true, features = ["derive"] }
 serde_plain.workspace = true
-regex = { workspace = true, optional = true }
+regex = { workspace = true }
 proxmox-network-types.workspace = true
-proxmox-schema = { workspace = true, optional = true, features = ["api-macro"] }
+proxmox-schema = { workspace = true, features = ["api-macro"] }
 proxmox-section-config = { workspace = true, optional = true }
 proxmox-node-status.workspace = true
 
 [features]
 default = []
-api-types = ["dep:regex", "dep:proxmox-schema", "dep:proxmox-section-config", "proxmox-network-types/api-types"]
+api-types = ["dep:proxmox-section-config", "proxmox-network-types/api-types"]
 # enable old-style answer file keys with underscores for backwards compatibility
 legacy = []
 
diff --git a/proxmox-installer-types/src/answer.rs b/proxmox-installer-types/src/answer.rs
index 9c6317ae..8bb9f0dd 100644
--- a/proxmox-installer-types/src/answer.rs
+++ b/proxmox-installer-types/src/answer.rs
@@ -41,6 +41,17 @@ proxmox_schema::const_regex! {
     pub SUBSCRIPTION_KEY_REGEX = r"^(?:pve[0-9]+|pbs|pmg)[cbsp]-[0-9a-f]{10}$";
 }
 
+proxmox_schema::const_regex! {
+    /// An email address using the regex for `<input type="email" />` elements
+    /// as defined in the [HTML specification].
+    /// Using that /should/ cover all possible cases that are encountered in the wild.
+    ///
+    /// It additionally checks whether the email our default email placeholder value.
+    ///
+    /// [HTML specification]: <https://html.spec.whatwg.org/multipage/input.html#valid-e-mail-address>
+    pub EMAIL_REGEX = r"^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$";
+}
+
 /// Schema for an optional Proxmox subscription key.
 #[cfg(feature = "api-types")]
 pub const SUBSCRIPTION_KEY_SCHEMA: proxmox_schema::Schema =
@@ -1229,3 +1240,14 @@ where
         _ => Ok(None),
     }
 }
+
+/// Validates an email address according to [EMAIL_REGEX]
+pub fn email_validate(email: &str) -> Result<()> {
+    if !EMAIL_REGEX.is_match(email) {
+        bail!("Email does not look like a valid address (user@domain.tld)")
+    } else if email == crate::EMAIL_DEFAULT_PLACEHOLDER {
+        bail!("Invalid (default) email address")
+    }
+
+    Ok(())
+}
-- 
2.47.3