Add null check for form name in switcher#2183
Conversation
WalkthroughThe pull request modifies the Changes
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 (
|
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
classes/helpers/FrmFormsHelper.php (1)
130-130: Consider using type coercion for better null handling.While the current fix works, you could make the code more robust by using type coercion to ensure
strip_tags()always receives a string:-$name = '' === $name || is_null($name) ? self::get_no_title_text() : strip_tags($name); +$name = '' === (string)$name ? self::get_no_title_text() : strip_tags((string)$name);This approach:
- Handles null values through type coercion
- Reduces complexity by eliminating the need for an explicit null check
- Ensures
strip_tags()always receives a string
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
classes/helpers/FrmFormsHelper.php(1 hunks)
🔇 Additional comments (1)
classes/helpers/FrmFormsHelper.php (1)
130-130: LGTM! The null check fixes the deprecation warning.
The addition of is_null($name) check properly handles cases where the form name is null, preventing the PHP deprecation warning when calling strip_tags().
I have a form with
nullfor a name, and noticed this message.