Comment 2 for bug 1651260

Thank you for opening the bug against the gui.

However, I do not think that this bug is invalid in the context of core. There's a discrepancy between the websocket api and the command line client that is not well documented, and that is breaking clients that attempt to talk to the websocket api.

I'm requesting one of the following:

1) Documentation on what the command line client is doing to manipulate empty keys so that clients like the gui or python-libjuju can perform the same manipulation.

2) A patch to the websocket gui so that it behaves in the same way as the command line client, without additional development work on the part of people writing clients.

Thank you.