🪲 Server Connect endpoint incorrectly nested under Responsive Sidebar

Wappler Version : 7.9.7
Operating System : W11
Server Model: NodeJS
Hosting Type: Docker
Extension: @benpley/wappler-responsive-sidebar

Description
When using the Responsive Sidebar (@benpley/wappler-responsive-sidebar) on a layout page with ID sidebar1, any Server Connect component appears nested under the sidebar in the Data Bindings panel.

Example:

sidebar1.serverconnect_testing.data.myApp

Expected:

serverconnect_testing.data.myApp

Steps to Reproduce

  1. Add Responsive Sidebar to a layout page (sidebar1).
  2. Add a Server Connect component.
  3. Open Data Bindings.

Hi Ben,

It looks like this issue is a bit like the one in this example. It has been around for a while now. I initially thought it was just a local problem, so I removed the extra prefixes myself and didn’t report it as a bug.

The dynamic bindings are adding a prefix of content. and the ID of the repeat region repeat1[0] to the notification_id.

scf_upd_notification_read.notification_read_notification_id.setValue(content.repeat1\[0\].notification_id)

Expected binding
scf_upd_notification_read.notification_read_notification_id.setValue(notification_id)

Button Element with incorrect dynamic on-click binding

<button class="btn btn-sm" type="button" dmx-on:click="run(\[{run:{name:'setNotificationReadId',outputType:'text',action:\`scf_upd_notification_read.notification_read_notification_id.setValue(content.repeat1\[0\].notification_id)\`}},{run:{name:'markNotificationRead',outputType:'text',action:\`scf_upd_notification_read.submit()\`}}\])" aria-label="Mark notification as read">
</button>