Class DatasetConditionDetail
- Namespace
- DatabentoDotNet.Historical
- Assembly
- DatabentoDotNet.Historical.dll
The condition of a dataset on a particular day.
public sealed record DatasetConditionDetail : IEquatable<DatasetConditionDetail>
- Inheritance
-
DatasetConditionDetail
- Implements
- Inherited Members
Remarks
Port of upstream's DatasetConditionDetail
(databento-rs/src/historical/metadata.rs:292-304). Returned by
metadata.get_dataset_condition, one entry for every date in the requested range —
including a date with no data at all, which is the only way a caller can tell "the range is
complete and empty" apart from "the response silently dropped a day".
Properties
Condition
The condition code describing the quality and availability of the data on Date.
public required DatasetCondition Condition { get; init; }
Property Value
Date
The day of the described data.
public required LocalDate Date { get; init; }
Property Value
LastModifiedDate
The date when any schema in the dataset on Date was last generated or modified, or null when no such date is known.
public LocalDate? LastModifiedDate { get; init; }
Property Value
Remarks
The one property on this record that is not required. Upstream's doc
comment says this "will be None when condition is Missing"
(metadata.rs:300-301) — but that is a description of what the API happens to send,
not a constraint this type enforces. On the wire last_modified_date is an
Option regardless of Condition
(#[serde(deserialize_with = "deserialize_opt_date")], metadata.rs:302-303), so
a null arriving on an Available day
deserializes here exactly as readily as one on a Missing day
— neither this property nor its converter rejects that combination.