nerves-project / property_table

93%

main: 93%

LAST BUILD ON BRANCH non-nil-previous-timestamp

branch: non-nil-previous-timestamp

CHANGE BRANCH

x

Reset

• non-nil-previous-timestamp
• bump-deps
• ci
• cleanup
• coveralls
• dependabot-automerge
• dependabot/hex/benchee-1.4.0
• dependabot/hex/credo-1.7.11
• dependabot/hex/credo-1.7.12
• dependabot/hex/dialyxir-1.4.6
• dependabot/hex/ex_doc-0.35.1
• dependabot/hex/ex_doc-0.36.1
• dependabot/hex/ex_doc-0.37.0
• dependabot/hex/ex_doc-0.37.1
• dependabot/hex/ex_doc-0.37.2
• dependabot/hex/ex_doc-0.37.3
• dependabot/hex/ex_doc-0.38.0
• dependabot/hex/ex_doc-0.38.1
• dependabot/hex/ex_doc-0.38.2
• dependabot/hex/ex_doc-0.38.3
• dependabot/hex/ex_doc-0.38.4
• dependabot/hex/excoveralls-0.18.4
• dependabot/hex/excoveralls-0.18.5
• digit/options-spec-fix
• get-all-with-timestamps
• main
• raising_flush
• reduce-file-io
• rel-v0.2.5
• rel-v0.2.6
• rel-v0.3.0
• reuse
• reuse2
• subscribe-and-get

Build # 37c85533-4492-43e5-a1b2-2710b972efa8

Build Type

Pull #95

circleci

Committed by fhunleth

Commit Message

Set event previous timestamps as best as possible

Previously when events were sent on a property for the first time, the
`previous_timestamp` was `nil`. This was a typespec violation, but it
also made it hard to know how long the property was in the unknown
state. Depending on the use, an application could infer a default value
on the property. It could also assign an "unknown" value. Either way, it
could be useful to know how long it was in this state and `nil` didn't
help.

A side effect of this change is that all values set explicitly or
implicitly at startup will have the same timestamp. This could come in
handy.

Pull Request Pull Request #95: Set event previous timestamps as best as possible

Run Details

12 of 12 new or added lines in 3 files covered. (100.0%)

264 of 283 relevant lines covered (93.29%)

13.55 hits per line