You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion OpenMage could need a few new events around configuration alteration or deletion.
A general event such as core_config_data_delete_commit_after is already thrown, but maybe a core_config_data_delete_<xml_path> is more readable.
Expected behavior (*)
Add event so that a listener can be set on a specific xml_path. Or even specific value. (When XML Path changes from X to Y, or its new value is Z)
Benefits
For example, if you ever wanted to know that a specific path was changed for the system configuration, so that you can run an observer on it.
Additional information
Right now you may listen on core_config_data_delete_commit_after and the others, which kinda works but often adds boilerplate code to find out which xml path was changed. Or what the new value is (I think that info is even missing, aka old value <> new value)
The text was updated successfully, but these errors were encountered:
Description (*)
In my opinion OpenMage could need a few new events around configuration alteration or deletion.
A general event such as
core_config_data_delete_commit_after
is already thrown, but maybe acore_config_data_delete_<xml_path>
is more readable.Expected behavior (*)
Add event so that a listener can be set on a specific xml_path. Or even specific value. (When XML Path changes from X to Y, or its new value is Z)
Benefits
For example, if you ever wanted to know that a specific path was changed for the system configuration, so that you can run an observer on it.
Additional information
Right now you may listen on
core_config_data_delete_commit_after
and the others, which kinda works but often adds boilerplate code to find out which xml path was changed. Or what the new value is (I think that info is even missing, aka old value <> new value)The text was updated successfully, but these errors were encountered: