I just applied this patch @patrick but it throws this error in console:
BaseComponent.js:59 TypeError: Cannot read properties of null (reading 'startsWith')
at s._stateHandler (link.js:93:1)
at s.init (link.js:52:1)
at s.constructor (BaseComponent.js:48:1)
at s (api.js:5:1)
at t.hasOwnProperty.t.constructor (api.js:47:1)
at new s (api.js:5:1)
at s.$createChild (BaseComponent.js:139:1)
at s.<anonymous> (BaseComponent.js:271:1)
at Object.walk (dom.js:186:1)
at Object.walk (dom.js:191:1)
Edit: fixed by adding another href="/watch/" to the element.
So the problem is that I don't want a static 'href' in my repeat, which is why I left it out and only used dmx-bind:href="/watch/{{coursePublicRetrieve.data.queryCourse.id}}/{{id}}"
You can decide if this is desired behaviour or a bug
@Teodor analyse the dmx-bind:href expression and tell me if you consider it valid
This will be a fun bug report, given the inconsistency of expressions. This is not indicative of a user fault, but rather the fact there seem to be multiple ways to construct such expression through the Wappler editor.
For those unclear, it's my belief such kind of variable interpolation like {{id}} only works in HTML, not in Wappler attributes.
Edit:
The question that remains, was this working in AppConnect 1?
Tried different things, and it all works. Inside a repeat, internal anchor tags:
dmx-bind:href="direct_url_param"
dmx-bind:href="/some-path/id={{id_param}}"
dmx-bind:href="'/some-path/id=' + id_param"
No errors in console.
@Apple Using {{}} in expressions results in much cleaner code - without having to deal with single quotes and pluses. Given that we mostly live in the code view, its common for us to do bindings like this.