Skip to content

Conversation

@cbrasfield
Copy link
Contributor

It's not as pretty as #3

defaults:
_controller: '\Drupal\uceap_logging\Controller\FieldList::autocomplete'
requirements:
_permission: 'access content'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably be administer site configuration

$form['sensitive_fields'] = [
'#type' => 'textarea',
'#title' => $this->t('Sensitive Fields'),
'#description' => $this->t('Enter field machine names (one per line) that should have their values masked in entity change logs. When these fields are modified, they will appear in logs with masked values (e.g., ***MASKED***) instead of actual values.'),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Description should be restored.

@kurowski
Copy link
Member

kurowski commented Nov 6, 2025

OK I dig the autocomplete in general (I understand why you'd prefer select2 for UX but when I tested that branch locally the widget was missing?), however there's one big issue I discovered in testing this: base fields.

If we're autocompleting only on config fields, it implies that either base fields don't work or don't exist. But we def need to support (some) base fields. I'm not sure there's a reasonable way to do that? Unless you want to extend this to a custom widget where we select an entity type first, then fields on that entity, but that sounds like a lot of work...

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.

3 participants