Skip to content

Improvements to Flag Actions #3613

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

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

bordoni
Copy link
Member

@bordoni bordoni commented Feb 27, 2025

🎫 Ticket

No tickets for now.

🗒️ Description

After the release of 5.19.2 discussions around Stock handling and Attendee generation led us into identifying that we need more precision around Flag Action Markers as well as a way to guarantee that certain flag actions wont apply themselves again depending on its conditionals.

🎥 Artifacts

Before After
CleanShot 2025-02-27 at 17 09 02 CleanShot 2025-02-27 at 17 39 26

List of Items to Handle

  • Merge Decrease_Stock and Increase_Sales there are the same, but one is currently handling just individual capacity and the other shared capacity. Improve Stock and Sales handling for Tickets Commerce Flag Actions #3614
  • Merge Increase_Stock and Decrease_Sales there are the same, but one is currently handling just individual capacity and the other shared capacity. Improve Stock and Sales handling for Tickets Commerce Flag Actions #3614
  • Ensure that total_sales for tickets gets adjusted properly when refunds happen.
  • Determine a way to save the return of the handle() of each Flag Action so that we use it later to determine if we need to potentially execute that same given flag again.
  • Create a way for Flag Actions to have a default conditional method, which determines if that Flag Action can be executed for a given order.
  • Make sure all Date related markers use milliseconds, to reduce the risk of two calls happening exactly at the same time.

@bordoni bordoni added the hold Status: on hold–do not proceed with other status items. label Feb 27, 2025
@bordoni bordoni self-assigned this Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hold Status: on hold–do not proceed with other status items.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants