Feat/ticket actions

[dpanta94]

🎫 Ticket

ETP-975

🗒️ Description

Adds some Hooks for our tickets!

This feature is needed as part of the Waitlist feature. The reason is the waitlist will need to process waitlist subscribers exactly based on these hooks we are adding here.

A quick description about them:

Listening for stock changes is being done through the updated meta data. All of our tickets are using the meta key _stock for that. Since this is a SINGLE field that way is ideal. As long as the rest of our codebase keeps the field updated (it should happen already) the listener is working ok.

Listening for ticket date start and date end is a bit more complicated.

We want to avoid having to query all of our tickets every X amount of time to determine this. => Why ? Not required load and not reliable. e.g. a ticket goes on sale in the X meantime we didnt check.

Additionally, this is a personal opinion, but the whole WP ecosystem is event based. So i like going with events as well.

The functionality works as:

A single action is bound to the date time each ticket start date will be reached. The same happens for the ticket's end date. Whenever each one of those datetimes is updated the actions are updated as well.

That allows when the action fires, anyone who listens for it to take action.

The code has been fully tested for what is being added. Also performed a test to evaluate the performance of such a process.

🎥 Artifacts

✔️ Checklist

• Ran npm run changelog to add changelog file(s). More info here
• Code is covered by NEW wpunit or integration tests.
• Code is covered by EXISTING wpunit or integration tests.
• Are all the required tests passing?
• Automated code review comments are addressed.
• Have you added Artifacts?
• Check the base branch for your PR.
• Add your PR to the project board for the release.

[lucatume]

The code is good, I've proposed some changes that would not horribly alter its nature.