Closed ChrisPulman closed 3 months ago
do we need to class this as a breaking change? as the dynamicdata behaviour may have knock on effects?
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What kind of change does this PR introduce?
fix
What is the current behavior?
ReactiveUI 20.1.1 includes DynamicData 8 DynamicData 9 has an update to the Observable Change Set which introduces a default value, this results in a mismatch in count between V8 and V9
What is the new behavior?
the default value has been removed from the RoutingState CurrentViewModel
What might this PR break?
Execution should match previous versions
Please check if the PR fulfills these requirements
Other information: