AC2 beta, AC expression not evaluated outside of dmx-text

Wappler Version : 5.8.2 Beta channel
Operating System : mac
Server Model: node
Database Type:
Hosting Type:

Expected behavior

The following should render a button with either Save or Publish as its text

<button id="btn2" class="btn btn-primary" style="white-space: nowrap;" dmx-bind:disabled="!allow_save.value" dmx-on:click="run([{run:{action:`flow_validate_recipe.run()`,name:'flow_validate_recipe'}},{condition:{if:`recipe_valid.checked`,then:{steps:{condition:{if:`recipe.data.basics.publish_date&amp;&amp;query.action!=\'duplicate\'`,then:{steps:[{run:{action:`form_new_recipe.inp_submit_type.setValue(\'save\')`}},{run:{action:`form_new_recipe.submit()`}}]},else:{steps:{run:{action:`modal_recipe_publish.show()`}}}}}}}}])">{{(recipe.data.basics.publish_date && query.action != 'duplicate') ? 'Save' : 'Publish'}}
                <span class="spinner-border spinner-border-sm" role="status" dmx-show="form_new_recipe.state.executing &amp;&amp; (inp_submit_type.value.endsWith('publish') || inp_submit_type.value == 'save')"></span>
              </button>

Actual behavior

Moving to this (use dmx-text:) fixes the issue:

<button id="btn2" class="btn btn-primary" style="white-space: nowrap;" dmx-bind:disabled="!allow_save.value" dmx-on:click="run([{run:{action:`flow_validate_recipe.run()`,name:'flow_validate_recipe'}},{condition:{if:`recipe_valid.checked`,then:{steps:{condition:{if:`recipe.data.basics.publish_date&amp;&amp;query.action!=\'duplicate\'`,then:{steps:[{run:{action:`form_new_recipe.inp_submit_type.setValue(\'save\')`}},{run:{action:`form_new_recipe.submit()`}}]},else:{steps:{run:{action:`modal_recipe_publish.show()`}}}}}}}}])" dmx-text="(recipe.data.basics.publish_date && query.action != 'duplicate') ? 'Save' : 'Publish'">
                <span class="spinner-border spinner-border-sm" role="status" dmx-show="form_new_recipe.state.executing &amp;&amp; (inp_submit_type.value.endsWith('publish') || inp_submit_type.value == 'save')"></span>
              </button>

Yep, I got the same thing going on too!

Confirmed fix for me.

fixed in the extensions beta channel as inline update