Skip to content

feat(extension): configure PII entity types and custom regex from options page#540

Open
yjouini wants to merge 1 commit into
dataiku:mainfrom
yjouini:feat/extension-pii-config-wiring
Open

feat(extension): configure PII entity types and custom regex from options page#540
yjouini wants to merge 1 commit into
dataiku:mainfrom
yjouini:feat/extension-pii-config-wiring

Conversation

@yjouini

@yjouini yjouini commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Closes #458, Closes #459

Wires the Chrome extension options page to the server-side PII config endpoints introduced in #509 / #513. The config UI from #470 is brought over and re-pointed at the new contract; the backend changes in #470 are superseded by #509/#513, so this PR is extension-only.

Entity types (/api/pii/entities)

  • Checkbox grid of the model's detectable types from GET ({ available, disabled }). Checked = masked.
  • Unchecking adds a type to the backend's disabled (passthrough) set via POST { disabled: [...] }. A "Disable all / Enable all" toggle is included.
  • Unknown labels are rejected by the backend with 400 and surfaced inline.

Custom patterns (/api/pii/regexes)

  • Add named regexes (name + pattern) with a live match preview before saving.
  • POST replaces the whole set, so add/remove rebuild the list and re-POST. Each custom name then appears as a selectable entity type in the grid.

Notes

🤖 Generated with Claude Code

…ions page

Wire the Chrome extension options page to the new server-side PII config
endpoints introduced in dataiku#509/dataiku#513:

- Entity types: GET/POST /api/pii/entities ({available, disabled}),
  unchecking a type adds it to the disabled (passthrough) set.
- Custom patterns: GET/POST /api/pii/regexes, whole-set replacement on
  each add/remove; custom names appear as selectable entity types.

Config is stored server-side, so /api/pii/check needs no per-request
label list and background.js is unchanged.

Closes dataiku#458, Closes dataiku#459

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow user-defined custom regex patterns from the extension UI Make detected entity types configurable in the extension

1 participant