Skip to content

Adding section for new feature - useQueryString #4574

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

Merged
merged 6 commits into from
May 31, 2023
Merged

Conversation

joeynmq
Copy link
Contributor

@joeynmq joeynmq commented Apr 13, 2023

Proposed changes

The Engineering team has just released a new feature for Querystring API - useQueryString which allows customers to optionally add constraints to how parameters from query string are processed. Constraints include but not limited to, maximum and/or minimum length.

Currently, it is available on the NPM version but not on the CDN version.

Merge timing

ASAP once approved

Related issues (optional)

@joeynmq joeynmq added the KCS label Apr 13, 2023
@joeynmq joeynmq marked this pull request as ready for review May 24, 2023 09:07
@joeynmq joeynmq requested a review from a team as a code owner May 24, 2023 09:07
@joeynmq joeynmq requested review from forstisabella and removed request for a team May 24, 2023 09:07
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
@markzegarelli markzegarelli merged commit 983faa3 into develop May 31, 2023
@markzegarelli markzegarelli deleted the joeynmq-patch-1 branch May 31, 2023 21:00
@github-actions
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants