Skip to content

Use URLSearchParams instead of encodeURIComponent 4.1#5693

Merged
BalusC merged 2 commits into4.1from
Use_URLSearchParams_instead_of_encodeURIComponent_4.1
Mar 18, 2026
Merged

Use URLSearchParams instead of encodeURIComponent 4.1#5693
BalusC merged 2 commits into4.1from
Use_URLSearchParams_instead_of_encodeURIComponent_4.1

Conversation

@BalusC
Copy link
Copy Markdown
Contributor

@BalusC BalusC commented Mar 18, 2026

cc: @pizzi80

@BalusC BalusC changed the title Use url search params instead of encode uri component 4.1 Use URLSearchParams instead of encodeURIComponent 4.1 Mar 18, 2026
@BalusC BalusC added this to the 4.1.7 milestone Mar 18, 2026
@BalusC
Copy link
Copy Markdown
Contributor Author

BalusC commented Mar 18, 2026

Build green. Merging directly so we can move on.

@BalusC BalusC merged commit df461d7 into 4.1 Mar 18, 2026
3 checks passed
@BalusC BalusC deleted the Use_URLSearchParams_instead_of_encodeURIComponent_4.1 branch March 18, 2026 15:55
BalusC added a commit that referenced this pull request Mar 18, 2026
@pizzi80
Copy link
Copy Markdown
Contributor

pizzi80 commented Mar 19, 2026

@BalusC good job as always!

I wait that you merge all the other waiting PRs
so I can merge them in my fork before creating new PR... ok ?

besides code optimizations e normalization
I want to work on the dom replacing algorithm as I said many time ago

If everything will work as expected there is a chance to remove a lot of boilerplate code
that could simplify your migration to JS classes/modules or TS

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants