Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][MIG] account_statement_import_online_adyen #626

Conversation

NL66278
Copy link
Contributor

@NL66278 NL66278 commented Sep 25, 2023

This PR includes some changes to other modules to prevent interference with the workings of this module.

Note that the migrated import of statements has been tested and has extensive user tests, but that the bare minimum has been done for the technical migration of the account_statement_clearing_account module, as I have no extensive knowledge of reconciliation in 16.0.

@NL66278 NL66278 force-pushed the 16.0-mig-account_bank_statement_import_online_adyen branch 14 times, most recently from 5138cf4 to 7aebbea Compare September 29, 2023 16:54
@NL66278 NL66278 changed the title [WIP][16.0][MIG] account_statement_import_online_adyen [16.0][MIG] account_statement_import_online_adyen Sep 29, 2023
@NL66278 NL66278 force-pushed the 16.0-mig-account_bank_statement_import_online_adyen branch from 7aebbea to 514284f Compare October 18, 2023 08:19
NL66278 and others added 20 commits November 1, 2023 12:12
Put more information in the generated statement line. Also put the for users
more recognizable merchant ref in the name (Label) field, and put the psp reference in
ref.

With a small refactoring the information retrieved can also more easily be customized.
Move parsing code to separate class;
Break up large and unwieldy parsing method in separate methods.
@NL66278 NL66278 force-pushed the 16.0-mig-account_bank_statement_import_online_adyen branch from 514284f to 7ead4fa Compare November 1, 2023 11:14
Copy link

github-actions bot commented Mar 3, 2024

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Mar 3, 2024
@github-actions github-actions bot closed this Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants