rafmacalaba commited on
Commit
c26d381
·
1 Parent(s): 4894181

fix: validation updates now saved at top level, not nested in dataset_name

Browse files

human_validated, human_verdict, annotator, validated_at were being
incorrectly merged into dataset_name sub-object instead of the
dataset entry's top level. This caused verified count to never update.

Files changed (1) hide show
  1. app/api/validate/route.js +5 -5
app/api/validate/route.js CHANGED
@@ -64,14 +64,14 @@ export async function PUT(request) {
64
  return NextResponse.json({ error: `Dataset index ${dataset_index} out of range` }, { status: 400 });
65
  }
66
 
67
- // Merge updates into dataset_name (same level as judge_ fields)
 
 
 
68
  const currentEntry = pagesData[pageIdx].datasets[dataset_index];
69
  pagesData[pageIdx].datasets[dataset_index] = {
70
  ...currentEntry,
71
- dataset_name: {
72
- ...currentEntry.dataset_name,
73
- ...updates,
74
- },
75
  };
76
 
77
  // Save back
 
64
  return NextResponse.json({ error: `Dataset index ${dataset_index} out of range` }, { status: 400 });
65
  }
66
 
67
+ // Merge updates into the dataset entry.
68
+ // Fields like dataset_tag go at top level.
69
+ // Fields like human_validated, human_verdict, annotator, validated_at go at top level.
70
+ // Only dataset_name sub-fields (text, confidence, etc.) go inside dataset_name.
71
  const currentEntry = pagesData[pageIdx].datasets[dataset_index];
72
  pagesData[pageIdx].datasets[dataset_index] = {
73
  ...currentEntry,
74
+ ...updates,
 
 
 
75
  };
76
 
77
  // Save back