W3C home > Mailing lists > Public > public-device-apis-log@w3.org > September 2017

Re: [sensors] Undefined values makes GS a pain to work with using TypeScript

From: Mikhail Pozdnyakov via GitHub <sysbot+gh@w3.org>
Date: Tue, 19 Sep 2017 08:03:36 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-330461771-1505808205-sysbot+gh@w3.org>

Generally speaking `!!sensor.timestamp;` is an equivalent of `sensor.hasReading` but it is not just not that obvious.

-- 
GitHub Notification of comment by pozdnyakov
Please view or discuss this issue at https://github.com/w3c/sensors/issues/269#issuecomment-330461771 using your GitHub account

Received on Tuesday, 19 September 2017 08:04:12 UTC

This message: [ Message body ]
Next message: Kenneth Rohde Christiansen via GitHub: "Re: [sensors] Undefined values makes GS a pain to work with using TypeScript"
Previous message: Anssi Kostiainen via GitHub: "Re: [sensors] Fix Bikeshed custom header rendering bug"
In reply to: Kenneth Rohde Christiansen via GitHub: "[sensors] Undefined values makes GS a pain to work with using TypeScript"
Next in thread: Kenneth Rohde Christiansen via GitHub: "Re: [sensors] Undefined values makes GS a pain to work with using TypeScript"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:54 UTC