Skip to content

Fix/event ticketing block#33

Merged
gin0115 merged 2 commits intotrunkfrom
fix/event-ticketing-block
Aug 11, 2025
Merged

Fix/event ticketing block#33
gin0115 merged 2 commits intotrunkfrom
fix/event-ticketing-block

Conversation

@Ninodevo
Copy link
Contributor

@Ninodevo Ninodevo commented Aug 7, 2025

Changes proposed in this Pull Request

  • Adds a missing sprintf import.
  • Removes undefined products while the block is loading.

Testing instructions

  1. Install WooCommerce Box Office
  2. Create a Woo Ticket Product
  3. Create an event and add an event ticket block
  4. Select the event, save, and refresh
  5. The block should normally render

Summary by CodeRabbit

  • Bug Fixes

    • Improved product selection to ensure only valid products are included when selecting event tickets.
  • Chores

    • Updated internal imports for translation functions without affecting user-facing features.

@Ninodevo Ninodevo requested a review from gin0115 August 7, 2025 10:28
@coderabbitai
Copy link

coderabbitai bot commented Aug 7, 2025

Walkthrough

The changes involve two files within the event tickets block. In src/blocks/event-tickets/index.js, the getSelectedProducts function was updated to filter out undefined values from its result, ensuring only valid product objects are returned. In src/blocks/event-tickets/ticket-data-control/index.js, the import statement for the i18n module was adjusted to also import the sprintf function, in addition to the existing __ function. No changes were made to the declarations or signatures of exported or public entities in either file.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 07a1960 and e4d6781.

📒 Files selected for processing (2)
  • src/blocks/event-tickets/index.js (1 hunks)
  • src/blocks/event-tickets/ticket-data-control/index.js (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
src/blocks/event-tickets/index.js (1)
src/blocks/event-tickets/ticket-data-control/index.js (1)
  • item (661-724)
🔇 Additional comments (2)
src/blocks/event-tickets/ticket-data-control/index.js (1)

9-9: LGTM! Critical import fix.

Adding the sprintf import resolves the missing dependency error that occurs on line 351 where sprintf is used in the button label.

src/blocks/event-tickets/index.js (1)

150-154: LGTM! Defensive filtering prevents undefined product rendering.

The .filter(Boolean) addition properly handles cases where selected product IDs don't match any products in the items array, preventing undefined values from being passed to React components and causing rendering errors during loading.

✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@gin0115 gin0115 merged commit 36560e8 into trunk Aug 11, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants