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

setting a computed range causes "Missing 'min' or 'max' in 'range'" #55

Open
ashrafhasson opened this issue Mar 8, 2018 · 1 comment

Comments

@ashrafhasson
Copy link

ashrafhasson commented Mar 8, 2018

I tried to use the range-slider component with computed range property but that seems to cause noUiSlider to complain (eagerly) that it's "Missing 'min' or 'max' in 'range'." I tried to await the range value but it seems that it's immediately evaluating the resultant promise and failing to render with the error above.

I wonder how this is done or whether CP range is supported.

thanks

@ashrafhasson
Copy link
Author

I understand this is due to the fact that the range property must have already been settled when creating the noUISlider instance and that instance is created in the didInsertElement hook rather than didReceiveAttrs hook of the range-slider component? I wonder if it works to create my own wrapper component to wait for range to settle before rendering range-slider but even then I've already attempted to wait for promises to resolve in the template without much success.

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

No branches or pull requests

1 participant