Clarify CSV escaping and spreadsheet text import - #24
Open
manuelconcari-ai wants to merge 1 commit into
Open
manuelconcari-ai wants to merge 1 commit into
manuelconcari-ai wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CSV instructions say to wrap values in quotes but do not specify escaping embedded quotes. For example, wrapping the single value
normal",=1+1,"restwithout escaping creates three cells. CSV quotes also do not prevent spreadsheet formula interpretation.Specify doubled embedded quotes, preserved commas and line breaks, and records aligned with the header. Keep source text intact after the existing label/date/null formatting. Append one conditional line to the save confirmation recommending text import, with no guarantee for automatic opening or save/reopen.
This changes only the export skill's CSV section and its save confirmation. Prerequisites, mode selection, file naming, the saving workflow, the four existing confirmation lines, the Output Rules and the Markdown template remain unchanged.
One pre-existing inconsistency is worth noting without changing it here:
mode: publicomitsauthorin JSON and the per-report Author field in the Markdown template, while the Markdown table of contents and this CSV header list an Author column with no mode exception. This patch does not change which fields any mode exports.Validation: the patch applies and reverses at main 60d8813 and composes with the export-permission change in PR #22. A standard-library fixture preserves 28 synthetic values across the actual eleven-column header; a separate control shows naive wrapping splitting one value into three cells. The prepared file matches the documented patch byte for byte. No model-generated export, spreadsheet evaluation or mode filtering was tested.