Wappler 7 Beta 28
Node JS
Windows 10
In some many cases, I found out that I need to get some value and instead, I get whole path, so that turns to be wrong code being added.
Example:
Using this expression:
And then adding Unique Key:
When the correct value should be:
I faced this when also using some repeat values:
tableRepeat1.id_list100 instead of id_list100
If I'm not wrong, I previously reported this, but can't find the topic anymore
I can confirm this, but since no one else was reporting it, I assumed it was just me. I just got used to manually editing the code to what it should be.
As far as I can tell it only happens within repeat regions?
I will take some screenshots next time it happens for me.
Still on v7
This has plagued wappler for years.
As this issue is fixed in one area, it seems to pop up in another depending on whether it is a repeat,modal or otherwise.
Seem to recall previous reports on this issue.
Could you indicate when this exactly happens and what is your current selection in the App Structure tree?
Because if I try to select a server connect as repeating expression for repeater and then pick unique key expression - it is all exactly as it should without long path ...
So I can't really replicate the issue
Next time it happens i wll grab details for you.
Same, I have bookmarked this bug and will provide exact details next time. I'm sure it will come up soon.
I have managed to get it to happen in testing. It does happen when setting the route parameter of a link for example.
<a href="404/{{tableRepeatWorkshops[0].ws_id}}">{{ws_office}}</a>
And as a Dynamic Attribute -> Link
<a href="javascript:void(0);" dmx-bind:href="'404/'+tableRepeatWorkshops[0].ws_id">{{ws_office}}</a>
Ignore the sloppy mess in the screenshot. The whole purpose was to recreate the problem. Not a real project page.
@George do you need more info about this? O have you found the issue?
