Remote bindings missing when spaces (*) involved

[justparking]

(*) could be more than just spaces.

As shown below,

Given the raw data below (see screenshot):

The web user interface has a problem rendering the data (see below). Notice the blanks when there is supposed to be data. I believe it's related to spaces in the names of the remote events/actions.

And when I remove the spaces, it all works as it should.

[mcartmel]

I'm having trouble replicating this. Spaces seem to work ok for me. Can you set up something to show the problem?

[justparking]

I haven't been able to reproduce this anymore. Closing.

[scroix]

This issue still persists.

The bindings exist in the nodeConfig.json and, they appear wired, and they function.

However, they don't actually render in the UI.

I isolated the node to a new host, and the behavior persisted. I've packaged this up for perusal.

Interestingly... If you delete all the bindings (for some reason the in-line editor doesn't work in this case) all the bindings reappear, despite the file missing the bindings.

example_unrendered.zip

P.S. The JSON is valid.

[justparking]

Have managed to reproduce using your example.

@mcartmel Will leave example running.

[mcartmel]

Just have a moment to look over this issue.

I note that the name of the binding is:
Member MM-MT Media Films Status
But in the nodeConfig.json, the name of the binding is (note the extra spaces around the hyphen):
Member MM - MT Media Films Status

The binding will work because those spaces are ignored, but the UI will see them as being different; If you remove the spaces around the hyphen then it renders correctly. I'll see if I can make the UI ignore differences like this.