Semantic-Org/Semantic-UI · warning
{name} must be exactly "{ruleValue}"
Error message
{name} must be exactly "{ruleValue}" What it means
Default prompt for the Semantic UI Form `isExactly` rule (settings.rules.isExactly, form.js:1435). Performs case-SENSITIVE equality between the value and `{ruleValue}`. Shown when they are not strictly equal (including case).
Source
Thrown at src/definitions/behaviors/form.js:1263
url : /(https?:\/\/(?:www\.|(?!www))[^\s\.]+\.[^\s]{2,}|www\.[^\s]+\.[^\s]{2,})/i
},
text: {
unspecifiedRule : 'Please enter a valid value',
unspecifiedField : 'This field'
},
prompt: {
empty : '{name} must have a value',
checked : '{name} must be checked',
email : '{name} must be a valid e-mail',
url : '{name} must be a valid url',
regExp : '{name} is not formatted correctly',
integer : '{name} must be an integer',
decimal : '{name} must be a decimal number',
number : '{name} must be set to a number',
is : '{name} must be "{ruleValue}"',
isExactly : '{name} must be exactly "{ruleValue}"',
not : '{name} cannot be set to "{ruleValue}"',
notExactly : '{name} cannot be set to exactly "{ruleValue}"',
contain : '{name} must contain "{ruleValue}"',
containExactly : '{name} must contain exactly "{ruleValue}"',
doesntContain : '{name} cannot contain "{ruleValue}"',
doesntContainExactly : '{name} cannot contain exactly "{ruleValue}"',
minLength : '{name} must be at least {ruleValue} characters',
length : '{name} must be at least {ruleValue} characters',
exactLength : '{name} must be exactly {ruleValue} characters',
maxLength : '{name} cannot be longer than {ruleValue} characters',
match : '{name} must match {ruleValue} field',
different : '{name} must have a different value than {ruleValue} field',
creditCard : '{name} must be a valid credit card number',
minCount : '{name} must have at least {ruleValue} choices',
exactCount : '{name} must have exactly {ruleValue} choices',
maxCount : '{name} must have {ruleValue} or less choices'
},
View on GitHub (pinned to 597843ab84)
Solutions
- Type the exact expected string including case.
- If case should not matter, switch to the `is` rule.
- Normalize the value (e.g. strip zero-width chars) before validation.
- Provide a custom `prompt`.
Example fix
// before
rules: [{ type: 'isExactly[Admin]' }] // 'admin' fails
// after
rules: [{ type: 'isExactly[Admin]', prompt: 'Type exactly: Admin' }] Defensive patterns
Strategy: validation
Validate before calling
const expected = 'Admin';
if ($field.val() !== expected) { /* warn */ } Type guard
const matchesExactly = (v, t) => v === t;
Prevention
- Strip zero-width/unicode lookalikes from pasted input before comparing.
- Use is for case-insensitive matching.
- Provide an explicit prompt so users know case matters.
When it happens
Trigger: `{type:'isExactly[Admin]'}` with input `admin`, `ADMIN`, or any different string.
Common situations: Case-sensitive confirmations (security codes, role names), users pasting with auto-correct changing case, or copy-paste introducing invisible characters.
Related errors
- {name} must be "{ruleValue}"
- {name} cannot be set to exactly "{ruleValue}"
- {name} must contain exactly "{ruleValue}"
- {name} cannot contain exactly "{ruleValue}"
- {name} must be a valid url
AI-assisted analysis of Semantic-Org/Semantic-UI@597843ab84 (2026-08-13).
Data as JSON: /api/errors/3837d9c0dc2b6af8.
Report an issue: GitHub.