Skip to content

Fix import issue with conditonal logic#2472

Merged
Crabcyborg merged 1 commit into
masterfrom
fix_issue_with_importing_conditional_logic
Aug 22, 2025
Merged

Fix import issue with conditonal logic#2472
Crabcyborg merged 1 commit into
masterfrom
fix_issue_with_importing_conditional_logic

Conversation

@Crabcyborg

Copy link
Copy Markdown
Contributor

I noticed that quiz outcomes weren't importing properly. The fields were all unmapped.

This update adds another substring that should be safe to replace when importing data, that could possibly catch other similar issues - not just conditional logic.

@coderabbitai

coderabbitai Bot commented Aug 22, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Extends FrmFieldsHelper::switch_field_ids to include additional string replacement rules for conditional logic references, mapping occurrences of _field":"<old_id>"," to _field":"<new_id>", alongside existing replacements for [if], [foreach], and field_id patterns. No signature or control-flow changes.

Changes

Cohort / File(s) Summary of Changes
Field ID replacement enhancements
classes/helpers/FrmFieldsHelper.php
Added replacement rules to translate conditional-logic references (_field":"<old>","_field":"<new>",") when switching field IDs; existing replacement map for [if], [foreach], and field_id preserved.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 PHPStan (2.1.17)

Note: Using configuration file /phpstan.neon.
Invalid configuration:
Unexpected item 'parameters › strictRules'.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix_issue_with_importing_conditional_logic

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • 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.
  • 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 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/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
classes/helpers/FrmFieldsHelper.php (2)

1602-1605: Also handle end-of-object and escaped-quote cases

Right now this only matches when the _field property is followed by a comma and uses unescaped quotes. It can miss:

  • last property in an object: "_field":"<id>"}
  • strings that have been escaped once: _field\":\"<id>\",\" or _field\":\"<id>\"}

Add a few more targeted patterns to cover those without switching to regex.

 			// This covers conditional logic.
 			$replace[]      = '_field":"' . $old . '","';
 			$replace_with[] = '_field":"' . $new . '","';
+			// Handle end-of-object as well.
+			$replace[]      = '_field":"' . $old . '"}';
+			$replace_with[] = '_field":"' . $new . '"}';
+			// Handle escaped quotes (content embedded in another JSON/string layer).
+			$replace[]      = '_field\":\"' . $old . '\",\"';
+			$replace_with[] = '_field\":\"' . $new . '\",\"';
+			$replace[]      = '_field\":\"' . $old . '\"}';
+			$replace_with[] = '_field\":\"' . $new . '\"}';

1602-1605: Consider numeric JSON values for _field (if any)

If any stored conditional logic uses numeric IDs without quotes (e.g., "_field":123,), the current replacements won’t fire. If that exists in the wild, add numeric variants. If everything is consistently strings, ignore this.

+			// Optional: numeric JSON values (only if we ever store IDs as numbers).
+			$replace[]      = '_field":' . $old . ',';
+			$replace_with[] = '_field":' . $new . ',';
+			$replace[]      = '_field":' . $old . '}';
+			$replace_with[] = '_field":' . $new . '}';
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 6f91de1 and 1304a0d.

📒 Files selected for processing (1)
  • classes/helpers/FrmFieldsHelper.php (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: PHP 8 tests in WP trunk
  • GitHub Check: PHP 7.4 tests in WP trunk
  • GitHub Check: Cypress
  • GitHub Check: Cypress
  • GitHub Check: Run PHP Syntax inspection (8.3)
  • GitHub Check: PHP 7.4 tests in WP trunk
  • GitHub Check: PHP 8 tests in WP trunk
🔇 Additional comments (2)
classes/helpers/FrmFieldsHelper.php (2)

1602-1605: Good catch: cover conditional-logic references ending with _field

The added replacement safely targets JSON-encoded conditional logic references like "..._field":"<id>", and plugs an obvious hole that caused unmapped fields on import. Nicely localized and consistent with existing replacement strategy.


1602-1605: Please add targeted PHPUnit tests for conditional‐logic JSON and quiz‐outcome payloads

Based on the scan results, we didn’t find any existing tests or code paths that cover all of these edge cases for the _field remapping in switch_field_ids:

• JSON blobs where _field appears mid-object with a trailing comma (covered by your replacement on lines 1602–1604)
• JSON blobs where _field is the last property in an object (no trailing comma)
• Double-encoded or escaped-quote variants (e.g. _field\":\"…)
• Quiz-outcome payloads that include unmapped fields

We should ensure each of these scenarios is exercised by a regression test in tests/phpunit/fields/test_FrmFieldsHelper.php. I can help draft sample payloads and assertions if that’s useful.

@Crabcyborg
Crabcyborg merged commit b331b17 into master Aug 22, 2025
32 of 34 checks passed
@Crabcyborg
Crabcyborg deleted the fix_issue_with_importing_conditional_logic branch August 22, 2025 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant