Skip to content

return errors when people ask for historical values #38

@williamcodes

Description

@williamcodes

If you're not going to support historical values, which seems to be the case based on #9, the gem should return an error instead of nil when someone attempts to get a reading from the past.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions