Skip to content
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

closes #2480: Ability to pass options to qs for payload parsing #2538

Merged
merged 1 commit into from May 21, 2015

Conversation

@boneskull
Copy link
Contributor

@boneskull boneskull commented May 18, 2015

  • added optional qsParserOptions parameter to Request.setUrl()
  • added test illustrating use case prompting #2480
  • updated API.md to reflect new parameter; added info about stripTrailingSlash as well
- added optional `qsParserOptions` parameter to `Request.setUrl()`
- added test illustrating use case prompting hapijs#2480
- updated `API.md` to reflect new parameter; added info about `stripTrailingSlash` as well

_Available only in `'onRequest'` extension methods._

Changes the request URI before the router begins processing the request where:
- `url` - the new request path value.
- `stripTrailingSlash` - if truthy, strip the trailing slash from the path.
Copy link
Contributor

@hueniverse hueniverse May 19, 2015

s/truthy/true and specify the default value false (Defaults to false).

@hueniverse hueniverse self-assigned this May 21, 2015
@hueniverse hueniverse added this to the 8.5.0 milestone May 21, 2015
hueniverse pushed a commit that referenced this issue May 21, 2015
closes #2480: Ability to pass options to qs for payload parsing
@hueniverse hueniverse merged commit 4950872 into hapijs:master May 21, 2015
1 check passed
hueniverse added a commit that referenced this issue May 21, 2015
@boneskull
Copy link
Contributor Author

@boneskull boneskull commented Jun 1, 2015

thanks!

@boneskull boneskull deleted the hapi-2480 branch Jun 1, 2015
@lock
Copy link

@lock lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants