Skip to content

ISSUE-263: CSV RFC 4180 compliance#264

Open
DiegoPino wants to merge 10 commits into2.1.0from
ISSUE-263
Open

ISSUE-263: CSV RFC 4180 compliance#264
DiegoPino wants to merge 10 commits into2.1.0from
ISSUE-263

Conversation

@DiegoPino
Copy link
Copy Markdown
Member

See #263

WIP. This does not deal with existing AMI CSVs that could have been wrongly escaped double quotes or any other character, from external or internal sources

Also no testing has been made since we don't have the multi sources CSVs yet

@DiegoPino DiegoPino self-assigned this Mar 10, 2026
…limited strings OR JSON , but both. Processing might be slower, but more precise

@alliomeria as explained in slack, PHP decodes some primitives as JSON. With this new approach, when we check for Strings we discard ANY JSON that would end in an ARRAY (when decoded) and instead treat them as strings. Then we re-parse the same data (more time processing but once does not do LoD of a complete AMI set in realtime over and over, so that is Ok) as JSON. This also allows Mixed case CSVs, where some rows are simple strings to be processed by One Metadata Display, but other rows proper JSON, and still have LoD reconciliation
Will be used to pre-check on an Hook Update existing AMIs that have changed date prior to the request time (run time) of the hook
Won't commit yet the hook bc the post/update logic is still missing (new tab at an AMI set + a warning letting the user know the attached CSV needs to be fixed (automatically or manually).

This function could also be used on "replace/insert/add CSV" to any AMI set
…at was detected as "escaped" and needs to be fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant