Gravity Wiz Weekly #68
Support Optimizations, TypeScript, Loading UX.
Greetings, wizards. ?
We hope you had a very Happy Easter and, of course, you enjoyed the second episode of Game of Thrones! I’m writing this Sunday afternoon so we don’t know exactly how you’ll be feeling tomorrow when you read this…
This week, Scott and I continued our focus on optimizing support by tackling a couple common requests we get for Nested Forms. You don’t know Scott yet but you can expect a proper introduction soon. See the change log below for the full deets.
Clay busted out a new spell-book and converted Populate Anything’s JavaScript to TypeScript! This will allow us to deliver new delightful features and bug fixes more quickly. I spent a little time with Populate Anything this week as well, working on some upcoming improvements to the UX of our loading indicators. Here’s a sneak peak!
Alright, wizards. Until next week. ⚡️
Resources
Limit Choices | Shared Limits
We’ve restored support for sharing limits across multiple forms. This allows fields on different forms to share the same inventory pool.
Gravity Perks
Gravity Forms Nested Forms (v1.0-beta-7.5)
- Updated how markup for Nested Form field merge tags (individually and in {all_fields}) is generated.
- Added “nested-entries-all” template to allow overriding the the markup generated for Nested Form field merge tags (individually and in {all_fields}).
- Updated Display Fields setting name to “Summary Fields” and improved description to alleviate customer confusion on its purpose.
Gravity Forms Populate Anything (v1.0-beta-2.46)
- The wizards busted out their new spellbook and converted Populate Anything’s JavaScript to TypeScript! This will allow them to deliver new delightful features and bug fixes more quickly.
- Fixed issue where PA settings showed based on field type but did not account for input type.
- Added support for post_name property when filtering and populating posts.
