Fix #2945: Fix error caused by Layer Filter when operation field is empty#2981
Merged
offtherailz merged 1 commit intogeosolutions-it:2018.02.00from Jun 11, 2018
Merged
Conversation
…tion field is empty
offtherailz
approved these changes
Jun 6, 2018
offtherailz
pushed a commit
to offtherailz/MapStore2
that referenced
this pull request
Jun 20, 2018
…tion field is empty (geosolutions-it#2981)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fix error caused by Layer Filter when operation field is empty
Issues
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
Does this PR introduce a breaking change?