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
Is your feature request related to a problem? Please describe.
Currently, we split for each entity, module, a specific YAML file such as : magento/module-sales.yaml , magento/module-quote.yaml, magento/module-customer.yaml, adyen/module-payment.yaml
For these 3 entities, let says that I want to define a limit : 30 or change the interval day in a sql request in a where parameter
But as we work on different project with different needs, the limit value could be changed depending on the project.
It would be nice if we could define custom variables at the top of the config.yaml file, and each yaml file (extends) would inherited
Also, the custom variables could be also defined in each yaml file, not necessarily in the config.yaml
It's already possible but only for a few parameters.
In converter definition:
condition
In table definition:
where
sort_order (i've never tested it though)
skip_conversion_if
It doesn't work with limit because gdpr-dump currently requires an integer value for this parameter. And if we allowed string values, it still would not work with some database engines (e.g. mariadb does not allow sql variables in limit clause).
Is your feature request related to a problem? Please describe.
Currently, we split for each entity, module, a specific YAML file such as : magento/module-sales.yaml , magento/module-quote.yaml, magento/module-customer.yaml, adyen/module-payment.yaml
For these 3 entities, let says that I want to define a limit : 30 or change the interval day in a sql request in a where parameter
But as we work on different project with different needs, the limit value could be changed depending on the project.
Describe the solution you'd like
It would be nice if we could define custom variables at the top of the config.yaml file, and each yaml file (extends) would inherited
Also, the custom variables could be also defined in each yaml file, not necessarily in the config.yaml
Regards
The text was updated successfully, but these errors were encountered: