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

Suggestion to collapse LastKnownValue and HistoricalValue #42

Open
graemewelton opened this issue Mar 12, 2025 · 0 comments
Open

Suggestion to collapse LastKnownValue and HistoricalValue #42

graemewelton opened this issue Mar 12, 2025 · 0 comments

Comments

@graemewelton
Copy link

To simplify value interface implementation, and use, I would like to suggest collapsing LastKnownValue and HistoricalValue into a single interface (name TBD), where the only query difference is the time range specification.

To query the last known value, omit the time range query parameter(s). Response MUST be a single-item array.

To query a point in the past, or a time range, specify the time range query parameter(s). Response MUST be at least a single-item array, but will most likely be a multi-item array, ordered by timestamp.

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