The Model Target OpenAPI spec and the Web API Authentication page document State-Based Model Targets, which the mock has no support for:
stateBasedConfigurationJsonString on each model. When present, a State-Based Model Target dataset is created instead of a regular one.states on each view, an array of state names which must be a subset of the states defined in the state configuration JSON, and which defaults to all states when omitted.- The
modeltargets.statebasedmodeltarget.all and modeltargets.advancedstatebasedmodeltarget.all scopes.
Acceptance criteria
- Dataset creation accepts
stateBasedConfigurationJsonString and per-view states.
states entries are validated against the states declared in the state configuration JSON.- Verified fake tests cover creating a state-based dataset and the subset validation error, subject to the test account having the required scope.
- Any part which cannot be verified against a real database is documented in
docs/source/differences-to-vws.rst.
Scope enforcement is tracked separately in #3345, and general creation validation in #3193.
The Model Target OpenAPI spec and the Web API Authentication page document State-Based Model Targets, which the mock has no support for:
stateBasedConfigurationJsonStringon each model. When present, a State-Based Model Target dataset is created instead of a regular one.stateson each view, an array of state names which must be a subset of the states defined in the state configuration JSON, and which defaults to all states when omitted.modeltargets.statebasedmodeltarget.allandmodeltargets.advancedstatebasedmodeltarget.allscopes.Acceptance criteria
stateBasedConfigurationJsonStringand per-viewstates.statesentries are validated against the states declared in the state configuration JSON.docs/source/differences-to-vws.rst.Scope enforcement is tracked separately in #3345, and general creation validation in #3193.