it is not populating extraction checks in the grid
this is the smapel response:
"extraction_checks": "{'file_type_check': {'status': 'Pass', 'insight': "File type 'pdf' is valid", 'recommendation': ''}, 'docs_count_check': {'status': 'Pass', 'insight': '12 pages extracted successfully', 'recommendation': ''}, 'empty_page_check': {'status': 'Pass', 'insight': 'All pages have text content', 'recommendation': ''}, 'all_empty_check': {'status': 'Pass', 'insight': 'Document has readable content', 'recommendation': ''}}",
I just need -
file_type_check, empty_page_check, all_empty_check
and also the insights is not visible it is going behind the table
and show full document name in the quality check details
I see the issues. I need to:
null for checks that don't exist in API response, causing them not to renderLet me fix these issues:
I've made the following fixes:
file_type_check, empty_page_check, all_empty_check) even if the API response doesn't contain them. If a check doesn't exist in the API response, it will show as "Skipped" with the config-based insight and recommendation.bottom-full instead of top-full) and increased the z-index to z-[200]. Also added hover:z-[100] on the parent to ensure proper stacking.break-all for long file names. Also adjusted the grid to md:grid-cols-4 to give more space to the document name field.this was the response
"extraction_checks": "{'file_type_check': {'status': 'Pass', 'insight': "File type 'pdf' is valid", 'recommendation': ''}, 'docs_count_check': {'status': 'Pass', 'insight': '12 pages extracted successfully', 'recommendation': ''}, 'empty_page_check': {'status': 'Pass', 'insight': 'All pages have text content', 'recommendation': ''}, 'all_empty_check': {'status': 'Pass', 'insight': 'Document has readable content', 'recommendation': ''}}",
but still it is showing skipped in the extraction but the status is pass inside extractiion_checks
please validate all subchecks status
I see the issue - the parseChecks function simply replaces all single quotes with double quotes. But the problem is when there's text like "File type 'pdf' is valid" - the inner single quotes around pdf will also be converted to double quotes, breaking the JSON parsing.
Let me fix this by using a more robust parsing approach:
The issue was that the simple replace(/'/g, '"') was breaking JSON parsing when there were single quotes inside string values like "File type 'pdf' is valid". The new parsing function handles Python-style dict strings more carefully by:
'status': to "status":): 'Pass' to : "Pass")You can send messages while the preview loads