fix: resolve duplicate data and optimize CSV/Excel export #2015
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.
PR Checklist
If you have any questions, you can refer to the Contributing Guide
What is the current behavior?
Data Duplication: When exporting data in JSON, YAML, or XML formats, the message data is incorrectly duplicated (appearing both at the top level and nested within a properties object).
CSV/Excel Formatting: The exported CSV and Excel files have suboptimal formatting, making it difficult to read or process individual messages correctly in spreadsheet software.
Issue Number
Example: #2006
What is the new behavior?
Fix Duplication: Removed the redundant data nesting in JSON, YAML, and XML exports. The output structure is now clean and flat where appropriate.
Optimize Export: Refactored the CSV and Excel export logic (streamExportData.ts) to ensure messages are correctly formatted, likely ensuring one message per row and proper column separation.
Does this PR introduce a breaking change?
Specific Instructions
N/A
Other information
N/A