fix for allowed_values == AnyValue in templates
#464
Merged
Conversation
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
cehbrecht
requested changes
Apr 3, 2019
Collaborator
cehbrecht
left a comment
cehbrecht
left a comment
There was a problem hiding this comment.
See comments to the code.
cehbrecht
approved these changes
Apr 3, 2019
Collaborator
cehbrecht
left a comment
cehbrecht
left a comment
There was a problem hiding this comment.
Tested with Emu and it seems to fix the issue.
Collaborator
|
@davidcaron merged. Thanks :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Overview
The
any_valueparameter was left out of theLiteralInputserialization, but the xml template response depends on it.Related Issue / Discussion
#456
Additional Information
Contribution Agreement
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)