-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Move break functionality to an add-on #8153
Comments
has someone picked this up? |
Do you know what needs to be done? |
Yes I have a top view idea of this. We need to create a new add on in zap-extensions and use that in zaproxy using interfaces and remove the actual break implementation in core. As I research more on it, I will take your help if stuck somewhere. |
Not quite for the second part, in the end there will be no break functionality in core (i.e. no interfaces needed). Move the functionality to an add-on and change existing add-ons to use it. We should also discuss if we want third-party add-ons to keep working while the transition happens. |
Worth noting that there are core PRs changing the break functionality. |
got it. thank you |
The break functionality does not need be in core and being in an add-on allows to enhance/fix it without the need to wait for a full release.
The text was updated successfully, but these errors were encountered: