fix: suppress removed entity error in gui status code

[Kruziikrel13]

Resolved #84

[Kruziikrel13]

Nevermind, this is a bandaid not a fix.

[Copilot]

Pull request overview

This PR fixes a panic that occurs when the GUI attempts to display the status of a deleted mod entry. The fix changes entry.enabled().unwrap() to use unwrap_or_default() instead, which returns false when a RemovedEntity error occurs.

Changes:

• Replaced unwrap() with unwrap_or_default() for the enabled status checkbox to prevent panics when entities are deleted

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The same RemovedEntity error can occur on line 115 where entry.name().unwrap() is called. This should also use unwrap_or_default() or similar error handling to prevent panics when entities are deleted.

[Copilot]

Using unwrap_or_default() silently defaults to false for deleted entities, which may mask legitimate errors. Consider filtering out removed entities from the mod list before rendering, or explicitly handling the error case with proper user feedback.

Suggested change

	checkbox(entry.enabled().unwrap_or_default())
	let is_enabled = match entry.enabled() {
	Ok(value) => value,
	Err(err) => {
	eprintln!("Failed to read enabled state for {:?}: {}", entry, err);
	false
	}
	};
	checkbox(is_enabled)

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
barnacle-gui/src/components/mod_list/mod.rs	0.00%	1 Missing ⚠️

Files with missing lines	Coverage Δ
barnacle-gui/src/components/mod_list/mod.rs	0.00% <0.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.