Josh Crawford

Ah, thanks for clarifying. So this is not possible in Formie 2, and was added in Formie 3 (see https://github.com/verbb/formie/issues/764 and https://github.com/verbb/formie/issues/1528). It's quite the large refactor, so back-tracking it...

You won't need to re-create anything, just the ability to reference Repeater fields in conditions will be available.

Formie 3 is only available for Craft 5 sorry, so it's going to have to be part of a larger update from Craft 4 to 5 for this.

By removing the `required` attribute on inputs. You could also add/remove the `disabled` attribute on things, which disables sending these fields to the server entirely. Your show/hide logic should include...

What about it doesn't work? Are the attributes being toggled? Is there a server-side error being thrown? Because you'll likely need to employ server-side checks as well for required fields.

I'd firstly recommend to get off the beta and onto the finalised 3.x releases as soon as possible. Beta releases should be treated as such, as not used in production....

This is a little tricky with Blitz, as if you have server rewrites setup, it's never going to even hit Craft/Formie to run this Twig code. I'm not sure if...

I think you're after the `templateHtml` [option](https://verbb.io/craft-plugins/formie/docs/developers/graphql#the-templateHtml-query). ```gql { formieForm(handle: "simpleForm") { templateHtml(options:"{\"renderJs\": true}") } } ``` One thing you'll want to do is set a Form Template and have...

I'm not sure how you're embedding your HTML, but I have just realised that using something like `innerHTML` isn't going to work for `` elements. They can't be evaluated with...

In light of this, just added `templateJs` and `templateCss` for separate handling. To get this early, run `composer require verbb/formie:"dev-craft-5 as 3.0.8"`. ```js const formHandle = 'sample'; const endpoint =...