# Change JSON field type to allow JSONC

**URL:** <https://discourse.nodered.org/t/change-json-field-type-to-allow-jsonc/36716>\
**Category:** Feature Requests\
**Created:** [29 November 2020 14:59 UTC](https://discourse.nodered.org/t/change-json-field-type-to-allow-jsonc/36716 "2020-11-29T14:59:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [29 November 2020 15:51 UTC](https://discourse.nodered.org/t/change-json-field-type-to-allow-jsonc/36716/2 "2020-11-29T15:51:02Z")

</div>

> [@Formatted Function Node with separate JS files](https://discourse.nodered.org/t/formatted-function-node-with-separate-js-files/1760):
>
> I'm a big Node-Red fan, and I use it everyday. We use the "Projects" feature, and use GitHub to manage version control of our flows. The PrettyPrint setting has given us the ability to curate changes, but we also write a number of custom functions. Within a flows\_\*.json file, the contents of a function have the line feeds (\n) escaped. As a result Github can't discern changes line changes within a Node-Red function in a diff. If a Node-Red function node was changed, the entire "func:" field is…

---

_[View the full topic](https://discourse.nodered.org/t/change-json-field-type-to-allow-jsonc/36716)._