Fix Alipay CSV parser for updated export format#233
Open
rennsax wants to merge 1 commit into
Open
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.
Description
Update the Alipay CSV parser to support the latest exported bill format.
The new Alipay CSV export removes one header/tips line before the transaction table, so the parser now skips 22 non-transaction lines instead of 23. The sample Alipay CSV file is updated accordingly.
Motivation and Context
Alipay changed the CSV bill format by removing one preamble line from the exported file. With the previous parser offset, the first transaction row could be skipped or parsed incorrectly. This change aligns the parser with the current Alipay export layout.
Dependencies
No new dependencies are required.
Type of change
How has this been tested?
Tests passed.
Is this change properly documented?
No.