Commit 7aae9bc
committed
Updated tests which expected
Previously, calling `SetValue(key, null)` would set the `TrackedRecord<T>.Value` to null, but wouldn't delete the record. This was confusing, if not buggy, and the behavior was fixed (3d1ad6b, 0bccf1f). In doing so, however, unit tests which validated the previous assumption broke, and needed to be updated.
This isn't expected to harm any actual implementations, as they should already be written to account for missing records, since this is the default when loading from the database. The null value scenario would only occur when updating previously saved values.SetValue(key, null) to maintain record1 parent 326e64c commit 7aae9bc
1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
220 | 220 | | |
221 | 221 | | |
222 | 222 | | |
223 | | - | |
| 223 | + | |
224 | 224 | | |
225 | 225 | | |
226 | 226 | | |
| |||
238 | 238 | | |
239 | 239 | | |
240 | 240 | | |
241 | | - | |
| 241 | + | |
242 | 242 | | |
243 | 243 | | |
244 | 244 | | |
| |||
262 | 262 | | |
263 | 263 | | |
264 | 264 | | |
265 | | - | |
| 265 | + | |
266 | 266 | | |
267 | 267 | | |
268 | 268 | | |
| |||
0 commit comments