Check classes input exists before setting value#2317
Conversation
WalkthroughThe update modifies internal logic within the JavaScript responsible for duplicating field layout classes in a form builder. Specifically, it adds a safety check to ensure the target input element exists before attempting to set its value when duplicating layout classes to a new field. No changes were made to public interfaces or exported entities. Changes
Possibly related PRs
Tip ⚡💬 Agentic Chat (Pro Plan, General Availability)
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms (6)
🔇 Additional comments (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:
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 (
|
Related ticket https://secure.helpscout.net/conversation/2911273467/227892
No clue how to replicate this since any field allowed in a field group supports layout classes.
The error indicates that a field in a group, getting duplicated, does not actually have a layout class setting.
Pre-release
formidable-6.21b.zip