Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISSUE-1: Started implementing UI to configure replacements #3

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

robiningelbrecht
Copy link
Owner

No description provided.

@robiningelbrecht
Copy link
Owner Author

@anotherjames Made a lot of progress. UI almost ready to use. Still have to implement the "Empty table" option.

@@ -83,10 +72,9 @@ public static function getInstance($dbSpec, $options, EventDispatcherInterface $
}

Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
// @TODO Combine with above dispatched event to allow changing empty tables?
if (!empty($config['empty_tables'])) {
$empty_tables = array_keys(array_filter($config['empty_tables']));
$options['structure-tables-list'] = $empty_tables;
}

I could be very wrong - as this is totally untested! - but I suspect this might be do the trick to implementing empty tables, as asked in #1 (comment) ?

As mentioned in the @TODO comment though, it should probably be 'alterable' - maybe the GdprReplacementsEvent could expanded to cover more than just replacements, so that both settings could be extended by modules looking to add their own tables?

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.

2 participants