Closed mikahpinegar closed 6 months ago
Pull flooding options from the backend?
trevor has an endpoint that will return all of the options that are in use for an attribute for a specific set of regions. example call below
{{selector_service_url}}/v2/attribute?label=flooding frequency®ions=17®ions=76
it contains a list of display label and value pairs that will be used for filtering. all of the possible labels should be mapped over and displayed on the front end. the corresponding values should be used to filter down the crops
What's wrong
What done looks like
Where the changes need to be made