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

defined operator.valuesLabels not visible #197

Open
ctrlaltdylan opened this issue Apr 18, 2020 · 1 comment
Open

defined operator.valuesLabels not visible #197

ctrlaltdylan opened this issue Apr 18, 2020 · 1 comment

Comments

@ctrlaltdylan
Copy link

ctrlaltdylan commented Apr 18, 2020

Describe the bug
When creating a custom operator, the valueLabels don't show even when they're defined. See the geoproximity operator in this codesandbox:

https://codesandbox.io/s/nice-sunset-7n6c3?file=/src/config.js

To Reproduce
The codesandbox tells the story, for some reason the valueLabels aren't showing as options.

Expected behavior
I expect the list of valueLabels to display when the field is chosen and you select the next operator.

Screenshots
valueLabels
Screen Shot 2020-04-18 at 2 33 05 PM

Actual behavior:

Screen Shot 2020-04-18 at 2 33 57 PM

Additional context
This is a custom operator using a custom type in conjunction with a couple other custom operators.

@ctrlaltdylan
Copy link
Author

Starting to understand the issue. I assumed that the 2 fields were supplied by the operator.geoproximity.valuesList property, but actually it's other fields with the same type - a.k.a. the geo type.

This presents a weird problem, the geo field only makes sense when comparing with another geo field with a modifier like number of miles/kilometers away.

I'll keep playing, but I didn't realize that the proximity comparison fields were not based on valuesList.

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

No branches or pull requests

2 participants