# Output new line character for Inject Node string

**URL:** https://discourse.nodered.org/t/output-new-line-character-for-inject-node-string/28257
**Category:** General
**Created:** [13 June 2020 00:02 UTC](https://discourse.nodered.org/t/output-new-line-character-for-inject-node-string/28257 "2020-06-13T00:02:08Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [13 June 2020 09:20 UTC](https://discourse.nodered.org/t/output-new-line-character-for-inject-node-string/28257/6 "2020-06-13T09:20:17Z")

</div>

> [@michaelblight](#):
>
> True, I regularly forget that strings, numbers etc are valid JSON by themselves

I didn't know that!

> [@michaelblight](#):
>
> Perhaps I can hide behind the excuse that the JSON selection shows as {}, which dupes me every time.

That does confuse me as I don't use it that often - I always debate whether I should stick a { before and } after my JSON text

I'd much prefer it didn't show them and then I would always think I should include them myself

Alternatively, if the default field entry was {} , then that would stop my confusion  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/7/6718036c08c00d21b4288576be44d8eb7d20d82b.png)

---

_[View the full topic](https://discourse.nodered.org/t/output-new-line-character-for-inject-node-string/28257)._