Params Initial Relocation #6933
Conversation
|
Add-on loads and works as expected. I still need to address the DB bits. Turns out there were not images/icons in use. |
|
|
||
| public ExtensionParams2() { | ||
| super(NAME); | ||
| this.setOrder(59); |
There was a problem hiding this comment.
I bumped this to 59 vs core 58.
kingthorin
force-pushed
the
migrate-params
branch
2 times, most recently
from
77cd1e0 to
76933e1
Compare
|
Great job! No new security vulnerabilities introduced in this pull requestUse @Checkmarx to reach out to us for assistance. Just send a PR comment with Examples: |
kingthorin
force-pushed
the
migrate-params
branch
2 times, most recently
from
08eff9c to
08bfcb1
Compare
|
This will have to be synced once zaproxy/zaproxy#9148 is merged. |
kingthorin
force-pushed
the
migrate-params
branch
2 times, most recently
from
966a468 to
46f8476
Compare
| @@ -0,0 +1,2 @@ | |||
| version=0.0.1 | |||
|
|
||
| zapAddOn { | ||
| addOnName.set("Params") | ||
| addOnStatus.set(AddOnStatus.RELEASE) |
addOns/params/src/main/java/org/zaproxy/addon/params/ExtensionParams2.java
Show resolved
Hide resolved
That would mean depending on a core snapshot wouldn't it? |
|
No, can use reflection. |
|
Oh like it'll just use the functionality if available, then later when targeting 2.17 or whatever it can use the code directly? |
kingthorin
force-pushed
the
migrate-params
branch
from
46f8476 to
a769bb4
Compare
Signed-off-by: kingthorin <[email protected]>
kingthorin
force-pushed
the
migrate-params
branch
from
a769bb4 to
2f7e7ee
Compare
I've ported these changes. |
3 participants
Initial relocation of the Params extension/add-on from core.