# \[APP\]\[Pro\] JSON Handler and Manipulator

**URL:** <https://community.homey.app/t/app-pro-json-handler-and-manipulator/66317>\
**Category:** Apps\
**Tags:** app, tools, homey-pro\
**Created:** [July 21, 2022, 9:01am UTC](https://community.homey.app/t/app-pro-json-handler-and-manipulator/66317 "2022-07-21T09:01:57Z")\
**Posts on this page:** 1\
**Showing post:** 87

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [April 9, 2024, 9:35am UTC](https://community.homey.app/t/app-pro-json-handler-and-manipulator/66317/87 "2024-04-09T09:35:03Z")

</div>

> [@mroek](#):
>
> The received JSON that I am wanting to parse _ **does contain spaces** _ in the key names, which is perfectly valid JSON. I would therefore strongly argue that this is a bug in the app.

Okay, update to version 1.2.9 and its resolved.  
What already would have resolved is, was placing a `$` in front of the bracket, **without the dot** (my bad).

By default, the `$.` was placed in front of it, if a user didn’t do that. That caused the “bug”.

But i have changed it to include only a `$` if it starts with a bracket.

Also, i have created a small script to see if only one property name is entered and if it contains non-ascii - non-word characters, and if so, place it within brackets.  
This means you can now enter the name without using brackets, which makes the card more readable:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/f/9f205de7c9ad71e035439aefeaaa7b76cfbd5fbd.png)

---

_[View the full topic](https://community.homey.app/t/app-pro-json-handler-and-manipulator/66317)._