fix: guard detailMatchesSelection against null detail/selectedEntry

Browse source

When both detail and selectedEntry are null (initial render or mid-navigation
while a detail fetch is in flight), detail?.summary?.entry_uid and
selectedEntry?.entry_uid both evaluate to undefined, making the equality
true and causing a crash on detail.latest_summary.

Add selectedEntry?.entry_uid != null guard so the condition short-circuits
false whenever there is no real selection.

...

This commit is contained in:

archivr-qa 2026-08-28 20:25:41 +02:00

parent 79ac44834e

commit 9b2ecb8d7b

No known key found for this signature in database

3 changed files with 4 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

49

crates/archivr-server/static/assets/index-BxBKvOHp.js Normal file

View file

File diff suppressed because one or more lines are too long