Two kinds of data in one row
A TennisExplorer results row shows the players, the scoreline and, in the columns beside them, the home and away odds. Visually they are the same table. Structurally they are the same response. It is very easy to treat them as the same kind of data, and they are not.
Where they differ
| Scoreline | Odds | |
|---|---|---|
| What it is | A record of an event that happened. | A price somebody published as their product. |
| Who produced it | The match, reported by the tournament. | Bookmakers, supplied to the site. |
| Default here | On. | Off. |
Why the default is off rather than the feature removed
Because a default is a recommendation and a removal is a verdict. The safer behaviour is what you get without making a decision, which is what a default is for. But an operator may have their own basis for using odds data — a licence, a jurisdiction, a purpose — and a tool that decides that on their behalf is not being careful, it is substituting its own compliance position for theirs.
If you turn it on
includeOdds adds the two columns and costs extra requests, so the default is cheaper as well as more conservative. Everything else about the run is unchanged. The decision, and the basis for it, is yours.
