-
Notifications
You must be signed in to change notification settings - Fork 11
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
PB-304: Treasurehunt layer not displayed #803
PB-304: Treasurehunt layer not displayed #803
Conversation
Passing run #1881 ↗︎
Details:
Review all test suite changes for PR #803 ↗︎ |
ad843c3
to
bd76269
Compare
Looks like this fixes the issue, nice! |
I still would like to now whats different, I did not find any difference in the initialization, and in the json file the key value is defined as empty string, somehow in the old viewer that must have been deleted to get an undefined |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's different I suspect is the way Javascript interprets a "falsy" value, if the key
received here is null
or false
the previous test wouldn't trigger, but with the way you now check for "falsy-ness" (with !
) now all those values (undefined
, null
, false
, 0
) will output true
with a !
prefix
bd76269
to
f36c00e
Compare
f36c00e
to
5a6710a
Compare
Test link