Re: [sensors] is doing weird things with frequency

Would changing the [init 
dictionary]( like
 so fix the issue?

dictionary SensorOptions {
  double? frequency = null;

The intent is for `frequency` to be `null` unless specified by the API
 consumer. I wrongly(?) assumed `double?` by itself defaulted to 
`null` if not value was set.

As a sidenote, sorry for not being more reactive on this front, but 
I'm still [in between 

GitHub Notification of comment by tobie
Please view or discuss this issue at using
 your GitHub account

Received on Friday, 2 September 2016 13:02:39 UTC