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

PB-304: Treasurehunt layer not displayed #803

Merged
merged 1 commit into from
Apr 24, 2024

Conversation

LukasJoss
Copy link
Contributor

@LukasJoss LukasJoss commented Apr 23, 2024

@github-actions github-actions bot added the bug label Apr 23, 2024
Copy link

cypress bot commented Apr 23, 2024

Passing run #1881 ↗︎

0 158 20 0 Flakiness 0

Details:

PB-304: Assign default value to olstyle property if key is empty string
Project: web-mapviewer Commit: 5a6710a1bd
Status: Passed Duration: 05:08 💡
Started: Apr 24, 2024 12:38 PM Ended: Apr 24, 2024 12:43 PM

Review all test suite changes for PR #803 ↗︎

@LukasJoss LukasJoss force-pushed the fix-PB-304-treasurehunt-layer-not-displayed branch 2 times, most recently from ad843c3 to bd76269 Compare April 23, 2024 14:12
@LukasJoss LukasJoss changed the title PB-304: Add 'hack' to display layer with wrong default value PB-304: Treasurehunt layer not displayed Apr 23, 2024
@pakb
Copy link
Contributor

pakb commented Apr 24, 2024

Looks like this fixes the issue, nice!

@LukasJoss
Copy link
Contributor Author

LukasJoss commented Apr 24, 2024

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

@LukasJoss LukasJoss marked this pull request as ready for review April 24, 2024 08:51
@LukasJoss LukasJoss requested a review from pakb April 24, 2024 08:51
Copy link
Contributor

@pakb pakb left a 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

@LukasJoss LukasJoss force-pushed the fix-PB-304-treasurehunt-layer-not-displayed branch from bd76269 to f36c00e Compare April 24, 2024 12:23
@LukasJoss LukasJoss force-pushed the fix-PB-304-treasurehunt-layer-not-displayed branch from f36c00e to 5a6710a Compare April 24, 2024 12:35
@LukasJoss LukasJoss merged commit a8c7cd9 into develop Apr 24, 2024
6 checks passed
@LukasJoss LukasJoss deleted the fix-PB-304-treasurehunt-layer-not-displayed branch April 24, 2024 12:43
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.

2 participants