Feature/order summary chart visibility #346
Draft
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.
What does this PR do?
Key Changes
Layout Configuration: Added support for vertical/horizontal layout configuration in Payments Summary Block. The layout can now be controlled via CMS configuration field, allowing cards to be displayed either stacked vertically or side-by-side horizontally.
Optional Fields Support: Made
overdueandtoBePaidfields optional in the Payments Summary Block. If a field is not configured in CMS, the corresponding card is not displayed. This allows displaying only one card when needed (e.g., only overdue or only toBePaid).Chart Integration: Integrated chart functionality directly into Payments Summary Block (similar to Orders Summary Block architecture). The chart is now an optional part of the Payments Summary Block instead of being a separate Payments History Block. This provides better layout control:
showChartistrue: Cards and chart are displayed side-by-side (flex-col lg:flex-row)showChartisfalseor chart is not configured: Cards stretch to full width (flex-col md:flex-row), allowing payments-summary to take full width when payments-history block is removed