LLL Field Validity Review / 項目値の定義適合点検

FAQ

Does it change my content? No. It reads published entries and the field definitions and shows counts and entry ids. No field value is shown, stored or sent anywhere.

Why would saved values not fit the definition? The editor refuses a non-fitting save, so mismatches appear after a definition change (a choice removed, a limit tightened), after an import, or after a direct write to the data. This plugin finds those old values.

Why is "required" never judged? The host stores a default (empty text, 0, false) when a required value is missing, so a plugin cannot tell a missing value from a real one. Required fields are listed under Unknown. A missing required text can still show up as a length-rule mismatch.

What is listed as Unknown? Field types this version does not know, references bound to a relation, patterns that could run slowly or are not valid expressions, rules the host does not apply to that type, and repeater sub-fields. They are skipped, never counted as valid.

What is not checked? URL and date format, Portable Text and image internals, multiSelect item counts, data keys that no longer exist in the definition, pending drafts and revisions.

Are 0, false and empty text treated as missing? No. They are values. A collection with no published entries gets no verdict.

Security

LLL Inc. / MIT / contact@lx3.cafe. Version 0.1.1.

Capabilities: content:read, schema:read only. One POST admin route requiring plugins:manage and a signed-in caller. No network, hooks, cron, storage, settings or writes of any kind. Field values are judged in memory and dropped at once; they are never put into the output or stored. The output holds counts, rule names and opaque entry ids only. Hidden and non-public collections are not read. The language code is validated against a strict pattern and the collection against the list of public collections. Patterns taken from field definitions are run only after an allowlist screen: literals, ., \d \w \s, escaped punctuation, simple character classes, one flat group of literal alternatives, ^ at the start and $ at the end, at most one length-varying quantifier (fixed {n} repeats are free), at most 256 characters; values over 1000 characters are not matched. Anything else, including repeated optional parts, adjacent repeats, nested groups, back-references and look-around, is listed as Unknown without being run. Output is plain text in a code block; labels have control characters removed and spreadsheet-formula prefixes neutralised.

Limits: 200 published entries per collection, 1000 per run, 400 rows, 48 KiB report; beyond these the result is marked partial.

Report issues privately with version and a redacted reproduction. Do not send tokens or private exports.

Changelog

0.1.1

Use the field validity name and scope in the catalog and admin menu.

0.1.0

First release: read-only check of saved published values against the current field definitions (type, closed choices, number bounds, text length, pattern, item counts).

Installation

Requires EmDash 1.4.0 or later (below 2). Install from the plugin registry or from the bundle in dist/. Open "Field Validity Review" in the admin, pick a language for the report (and optionally one collection or a language code), and press the button. Signing in with plugin-management permission is required. Nothing is configured and nothing is stored.