fix: Handle server response for mining areas; ensure areas state is set correctly for non-array responses
This commit is contained in:
@@ -28,7 +28,8 @@ export default function MiningAreasPanel({ turtles, selectedTurtle, apiUrl }) {
|
|||||||
const response = await fetch(`${apiUrl}/api/mining-areas`);
|
const response = await fetch(`${apiUrl}/api/mining-areas`);
|
||||||
if (response.ok) {
|
if (response.ok) {
|
||||||
const data = await response.json();
|
const data = await response.json();
|
||||||
setAreas(data);
|
// Server returns a flat array of formatted areas
|
||||||
|
setAreas(Array.isArray(data) ? data : (data.areas || []));
|
||||||
}
|
}
|
||||||
} catch (error) {
|
} catch (error) {
|
||||||
console.error('Failed to load mining areas:', error);
|
console.error('Failed to load mining areas:', error);
|
||||||
|
|||||||
Reference in New Issue
Block a user