Skip to content

Params Initial Relocation#6933

Open
kingthorin wants to merge 1 commit intozaproxy:mainfrom
kingthorin:migrate-params
Open

Params Initial Relocation#6933
kingthorin wants to merge 1 commit intozaproxy:mainfrom
kingthorin:migrate-params

Conversation

@kingthorin
Copy link
Member

Initial relocation of the Params extension/add-on from core.

@kingthorin
Copy link
Member Author

kingthorin commented Nov 21, 2025

Add-on loads and works as expected. Help doesn't work for some reason that I haven't been able to nail down. (I've compared vs spider and don't see the missing bit).

I still need to address the DB bits.

Turns out there were not images/icons in use.

@kingthorin kingthorin force-pushed the migrate-params branch 2 times, most recently from 77cd1e0 to 76933e1 Compare November 21, 2025 14:15
@psiinon
Copy link
Member

psiinon commented Nov 21, 2025

Logo
Checkmarx One – Scan Summary & Details2e55c256-3366-4de6-9021-03b0f53c73fe

Great job! No new security vulnerabilities introduced in this pull request


Use @Checkmarx to reach out to us for assistance.

Just send a PR comment with @Checkmarx followed by a natural language request.

Examples: @Checkmarx how are you able to help me? @Checkmarx rescan this PR

@kingthorin kingthorin force-pushed the migrate-params branch 2 times, most recently from 08eff9c to 08bfcb1 Compare November 21, 2025 14:21
@thc202
Copy link
Member

thc202 commented Nov 21, 2025

This will have to be synced once zaproxy/zaproxy#9148 is merged.

@kingthorin kingthorin force-pushed the migrate-params branch 2 times, most recently from 966a468 to 46f8476 Compare November 21, 2025 14:36
@@ -0,0 +1,2 @@
version=0.0.1
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

0.1.0?


zapAddOn {
addOnName.set("Params")
addOnStatus.set(AddOnStatus.RELEASE)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Different status?

@kingthorin
Copy link
Member Author

This will have to be synced once zaproxy/zaproxy#9148 is merged.

That would mean depending on a core snapshot wouldn't it?

@thc202
Copy link
Member

thc202 commented Nov 21, 2025

No, can use reflection.

@kingthorin
Copy link
Member Author

Oh like it'll just use the functionality if available, then later when targeting 2.17 or whatever it can use the code directly?

Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
@kingthorin
Copy link
Member Author

This will have to be synced once zaproxy/zaproxy#9148 is merged.

I've ported these changes.

@kingthorin
Copy link
Member Author

Let's proceed with this one for now. I'll tackle moving DB bits in another PR.

@kingthorin kingthorin marked this pull request as ready for review January 30, 2026 14:27
@kingthorin
Copy link
Member Author

kingthorin commented Jan 30, 2026

Not draft, DB will be done in another step.

See zaproxy/zaproxy#9210

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants