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

WPS: allowedValues and defaultValue support for WPS Input LiteralData #6897

Closed
sppigot opened this issue Sep 18, 2023 · 1 comment · Fixed by #7033
Closed

WPS: allowedValues and defaultValue support for WPS Input LiteralData #6897

sppigot opened this issue Sep 18, 2023 · 1 comment · Fixed by #7033
Assignees

Comments

@sppigot
Copy link
Contributor

sppigot commented Sep 18, 2023

For any literal input a WPS can specify a list of allowed values as a range or as a list of values e.g.

''''

ows:IdentifierKeelDepth</ows:Identifier>
ows:TitleKeel Depth</ows:Title>
ows:AbstractDraft of the landing boat</ows:Abstract>

<ows:DataType ows:reference="http://www.w3.org/TR/xmlschema-2/#float">float</ows:DataType>
ows:AllowedValues
<ows:Range ows:rangeClosure="closed">
ows:MinimumValue1.0</ows:MinimumValue>
ows:MaximumValue2.0</ows:MaximumValue>
</ows:Range>
</ows:AllowedValues>
2.0


''''

TerriaJS should read and require user input to follow the allowed values (range or list) and initialise the form field with the defaultValue. Currently, if I include a WPS LiteralData Input (KeelDepth) with an AllowedValues element, TerriaJS trips an error on the browser console with the message: "The parameter KeelDepth is not a supported type of parameter."

@nf-s nf-s assigned sixlighthouses and unassigned na9da Dec 21, 2023
@sixlighthouses sixlighthouses mentioned this issue Jan 22, 2024
4 tasks
@sixlighthouses
Copy link
Contributor

Draft PR #7033

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants