Wrong prefix within repeat

[ben]

Wappler Version : 5.2.2
Operating System : Windows 10
Server Model: NodeJS
Database Type: SQLite
Hosting Type: Wappler

1. No hasItems() - 4:42 and 5:19
2. Incorrect code - 6:30

dynamic-navbar

[ben]

@patrick, in a previous version of Wappler, this is the code that was created:

<div class="dropdown-menu" aria-labelledby="dropdown1">
      <a class="dropdown-item" href="#" dmx-repeat:repeat2="sub_navigation">{{sub_item}}</a>
</div>

In version 5.2.2, this is the code:

<div class="dropdown-menu" aria-labelledby="dropdown1">
     <a class="dropdown-item" href="#" dmx-repeat:repeat2="_['sub-navigation']">{{_['sub-item']}}</a>
</div>

Will the former code be compatible with the latter?

[George]

the difference Ben is that when you use dash in ID’s it has to be escaped as it isn’t a valid identifier. So it is escaped with _[‘xxx-xxx’]

In your previous example you used underscore which is fine and doesn’t need to be escaped.

I will check the wrong prefixing, it was an existing bug:

Selecting value from repeat inside flow prefixes with tableRepeat1[0]

Wappler Version : 5.1.4 Operating System : Win 10 Server Model: node Database Type: SQLite Hosting Type: Wappler own Sadly this bug is back again Expected behavior when selecting a value form repeat in flow parameter should be “id” Actual behavior What actually happens? Value is prefixed tableRepeat1[0].id See video pickerbug

[ben]

Geez, computers are dumb. I meant to place an underscore, I always do. The darn (r + n) thing didn’t recognise my mistake causing me hours of anguish.

Fortunately @George to the rescue and this whole post is no longer relevant.

Long live Wappler!

[Teodor]

Fixed in Wappler 5.2.3