pub fn point_aggregate(
document: &str,
variables: &Variables,
) -> Result<u64, NodeCountError>Expand description
The aggregate GitHub’s step 1 produces for one call of the one operation in
document, under variables: the number of requests needed to fulfil every
unique connection in the call, assuming each reaches its page-size limit.
This is point_cost’s input rather than its answer — the raw number before
the division by 100 and the rounding — exposed so a consumer can see what a
document is charged for, and so a change that moves a document’s price by
less than a whole point is still visible. A connection is resolved once per
parent node, so it adds the product of the page sizes strictly above it,
and its own page size does not appear in this number at all.
§Errors
Exactly the failures node_count returns, meaning exactly the same things:
the two answers come from one walk of one parse, so a document either yields
both or fails identically for either.