Linq: add option to include future timestamps when no time range is provided #320
Description
Proposal:
Provide a configurable option for including data with future timestamps when no time bounds are explicitly set.
Current behavior:
When a query has no time bounds set, the InfluxDB.Client.Linq library doesn't have a way to include data with future timestamps in the results (defaults to now()).
Desired behavior:
Data with future timestamps would be included in query results without hardcoding an arbitrary future stop date range when an explicit option is specified to override the default stop date range of now() (when no stop date range is explicitly set).
Alternatives considered:
The current workaround is to hardcode an arbitrary future stop date range to ensure data with future timestamps is included in query results. This has obvious downsides and testing future stop date ranges (curl -> api, not with this library) had some unpredictable results when going too far into the future.
Use case:
Data with future timestamps has domain-specific uses but at a minimum prediction statistics. The unknown nature of future data makes hardcoding an unrealistic method to maintain.