-
Notifications
You must be signed in to change notification settings - Fork 90
gw-conditional-logic-operator-does-not-contain.php
: Fixed rule value for does not contain
rule.
#1094
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
Conversation
…e for `does not contain` rule.
…e for `does not contain` rule.
WalkthroughThis change refines the integration of the "does_not_contain" operator in Gravity Forms conditional logic by inserting it after the "contains" operator, extending the global Changes
Possibly related PRs
Suggested reviewers
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
gravity-forms/gw-conditional-logic-operator-does-not-contain.php
Outdated
Show resolved
Hide resolved
…e for `does not contain` rule.
|
Context
💬 Slack: https://gravitywiz.slack.com/archives/C04RQJ232PQ/p1746134330652079
Summary
The does not contain rule renders select of dropdown, instead of the text box.
David's loom explaining the issue:
https://www.loom.com/share/fc3e8050e0284dc480247ad2e35112ff
This PR adds the override for
does_not_contain
operator as well. Loom Demo: https://www.loom.com/share/5eeed1dd533449eab06cef3088922defI had initially thought of the approach of using
However, the issue with this approach was that on first render the
field_rule_value_
was not defined yet, and we couldn't getdoes not contain
to render the string instead of the dropdown of the values (for this example). It did work fine on frontend and any refresh on the values by adding/removing more rules. However, this solution was clearly lacking the correct behaviour. The issue with this approach:https://www.loom.com/share/877e59bf2b9147e2aed59527754ec31e