Handling Wrong Data in CSV

[egekorkan]

Sometimes the imported CSV has wrong data but it does not fail the conversion, such as having number123 instead of number or holdingregister instead of HoldingRegister. This should be handled somehow. Below are some ideas:

• Reject the CSV input and push the user to go back to the CSV and reupload it. The errors should be saved as text so that the user can track what needs to be fixed
• Accept the input as today but show the errors and push the user to fix the errors on JSON (e.g. via replace all)
• Show a pop-up after the CSV conversion to render the CSV as a table and highlight the issues.

[Pranav-0440]

Hi @egekorkan,
I’d like to work on this issue by adding a validation step after CSV parsing
in ediTDor. The CSV will still be converted, but invalid values (e.g. wrong
register names or identifiers) will be detected and shown as warnings to
the user. Please let me know if this approach is acceptable.

[egekorkan]

@Pranav-0440 make sure to provide an example valid and invalid CSV with your PR :)

[TejInaco]

@Pranav-0440 Merge the two PR. Review of the files is in #195

Note this @Pranav-0440 : The general policy to require a human in the loop for new code contributions in the interest of reducing volunteer maintainer burden, this “good-first-issue” was specifically created and curated to give early programmers an easy way to onboard into the project and community. I discovered this particular performance enhancement and spent more time writing up the issue, describing the solution, and performing the benchmarking, than it would have taken to just implement the change myself. We do this to give contributors a chance to learn in a low-stakes scenario that nevertheless has real impact they can be proud of, where we can help shepherd them along the process. This educational and community-building effort is wasted on ephemeral AI agents.

[Pranav-0440]

Thanks for the clarification. I will recreate a clean PR by merging the two changes
and keeping only the CSV validation-related modifications. I’ll ensure the diff
is minimal and focused strictly on Issue #134.