# Flows/\*.json instead of flows.json?

**URL:** <https://discourse.nodered.org/t/flows-json-instead-of-flows-json/34043>\
**Category:** Core Development\
**Created:** [10 October 2020 10:48 UTC](https://discourse.nodered.org/t/flows-json-instead-of-flows-json/34043 "2020-10-10T10:48:01Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [19 October 2020 09:06 UTC](https://discourse.nodered.org/t/flows-json-instead-of-flows-json/34043/6 "2020-10-19T09:06:55Z")

</div>

> [@Stwissel](#):
>
> Beside configuration nodes, what else would need special attention?

If you look at the `/flow` api you can see how things have to be split up. Global configuration nodes and Subflow definitions need to be thought about.

In many ways, adding the logic to write the flows into separate files is the easy part.

If you're wanting to do this as an enhancement to the existing projects storage plugin, then you'll need to consider:

- how does NR know that a project's flows are split amongst multiple files rather than a single file?
- how does a user configure a project to split the flow files up?
- what UI changes does that drive through-out the project settings

We'd need to discuss a design around all of those elements.

---

_[View the full topic](https://discourse.nodered.org/t/flows-json-instead-of-flows-json/34043)._