You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Are you sure this is an issue with hapi or are you just looking for some help?
Definitely with hapi, although I don't know this is a bug or just undocumented behavior. It's unexpected, at the very least.
What are you trying to achieve or the steps to reproduce?
When a route prerequisite replies with an empty string, the resulting property assigned to request.pre is null, not the empty string as I was expecting.
I am not sure yet. This came up in nes as well where empty payload is sent as null. I need to come up with a consistent way to address it. I think I am not going to force '' into null anymore, but still treat both as empty payload.
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.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Are you sure this is an issue with hapi or are you just looking for some help?
Definitely with hapi, although I don't know this is a bug or just undocumented behavior. It's unexpected, at the very least.
What are you trying to achieve or the steps to reproduce?
When a route prerequisite replies with an empty string, the resulting property assigned to
request.pre
isnull
, not the empty string as I was expecting.This is because of
hapi/lib/response.js
Lines 82 to 87 in ec5eaca
What was the result you received?
null
What did you expect?
empty string
Context
The text was updated successfully, but these errors were encountered: