Closed malsyned closed 6 years ago
Calls to the pfstest-mock API are all over the core, which feels like a layering violation to me. Add a simple plugin API to pfstest-core that pfstest-mock can be registered with to break the cycle. Maybe a simple pfstest_list_t of plugins.
Where constructors are available, registration should be automatic.
Since registration can be automatic, plugins will also have to plug into pfstest_print_register_commands.
Calls to the pfstest-mock API are all over the core, which feels like a layering violation to me. Add a simple plugin API to pfstest-core that pfstest-mock can be registered with to break the cycle. Maybe a simple pfstest_list_t of plugins.