This code was modified by Gemini 2.5 as Agent inside Wappler <a class="nav-link" id="navTabsTerms" data-bs-toggle="tab" href="#" data-bs-target="#navTabTerms" role="tab" aria-controls="navTabs1_2" aria-selected="false" dmx-on:click="v_terms_status_filter.setValue(''); termsSort.set('sort','version_title'); termsSort.set('dir','desc'); sc_qry_terms.load({v_terms_status_filter: '', sort: 'version_title', dir: 'desc'}, true)"><i class="fas fa-file-contract fa-sm me-1"></i>Terms & Conditions</a>
When I come back to review this is what I see:
Usually this means AI hallucinated something that isn't 100% correct, so Wappler fails to show the properties. There isn't much one can do apart from doing detective work to see what was generated erroneously (by comparing to working code)
AI can work with HTML, Bootstrap, but Wappler-specific stuff is prone to more mistakes
Our parser for the actions wasn't taking spaces after ; into account (it wasn't ignoring them so that is why the actions couldn't be found to display their parameters.