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

[IMP] Allow to use the storage either from the payment mode or from the payment method #1279

Open
wants to merge 1 commit into
base: 16.0
Choose a base branch
from

Conversation

lmarion-source
Copy link

Initially, the storage was found only on the payment method. We added the storage at the payment mode level to allow different storage for different companies.

Copy link
Contributor

@AnizR AnizR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great initiative 👍

@AnizR
Copy link
Contributor

AnizR commented May 31, 2024

@acsonefho ping

@lmarion-source lmarion-source force-pushed the 16.0-improve_account_payment_method_fs_storage branch from a8c063e to c984316 Compare May 31, 2024 09:18
@lmarion-source lmarion-source force-pushed the 16.0-improve_account_payment_method_fs_storage branch 4 times, most recently from 4e4de5a to 23cc7e0 Compare June 10, 2024 11:30
@lmarion-source lmarion-source force-pushed the 16.0-improve_account_payment_method_fs_storage branch 2 times, most recently from 04970f2 to 8c6e721 Compare June 14, 2024 11:33
@lmarion-source lmarion-source force-pushed the 16.0-improve_account_payment_method_fs_storage branch 2 times, most recently from f550e6a to 43efe52 Compare June 17, 2024 13:23
@lmarion-source lmarion-source force-pushed the 16.0-improve_account_payment_method_fs_storage branch 2 times, most recently from 310d5cf to 4eba1a8 Compare June 19, 2024 09:43
@lmarion-source lmarion-source force-pushed the 16.0-improve_account_payment_method_fs_storage branch from 4eba1a8 to 786b357 Compare June 25, 2024 08:46
Copy link

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 Oct 27, 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.

3 participants