Skip to content

Clarify N+1 spec intention

What does this MR do and why?

The spec has been adjusted to clarify the intention of the N+1 behavior. Previously, the presence of incremental data in the N+1 service call was ambiguous due to subject caching. This has been made clearer now with multiple explicit calls to the service within the spec, both before and after adding new data.

Related to #440355 (closed)

Edited by Alex Pooley

Merge request reports