-
Notifications
You must be signed in to change notification settings - Fork 409
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
setting the default layer as object #3199
Conversation
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.
- Please add a unit test for this reducer default
- Add a unit test for autoMapUpdate epic (the effective issue)
suggestion: try to replicate the issue in autoMapUpdate test using the reducer (not fixed) for initial state (See how epics are tested here and there). Then apply your fix to verify that the problem is solved. You can even fix autoMapUpdate using layersSelector
wrap the state access correcly
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.
@baloola, this needs a PR to be backported to the stable branch 2018.02.xx too.
This needs to be done before the merge.
* Revert "Removes console logs from browser from karma testing output (#3207)" This reverts commit 264ef58. * Revert "Fix #3209 show/hide title translations in layer settings (#3210)" This reverts commit 415e63d. * Revert "Fixes #2669: use https version of geosolutions maven repo (#3182)" This reverts commit dc4084c. * Revert "Automatic definition of proj codes from configuration in OpenLayers maps (#3133)" This reverts commit 70ee3b9. * Revert "Fix #3192 setting the default layer as object (#3199)" This reverts commit fe50170. * Revert "Fix #2298 de-DE translation fix (#3205)" This reverts commit e39348a. * Revert "hiding div to allow playing/showing the video (#3188)" This reverts commit a7c9e66.
Description
solving the error resulted from the new update of chrome and firefox
Issues
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
What is the current behavior? (You can also link to an open issue here)
see #3192
What is the new behavior?
when the user access a an authorized map. the login prompt pops up and an error loading map massage is rendered in the middle of the screen.
Does this PR introduce a breaking change? (check one with "x", remove the other)
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
The default value of layer was replaced into an object. No unit-test was added since in all the pre-existing tests the layers value is already an object.