Is your feature request related to a problem? Please describe.
Our project is massive and split across several different yarn files. Sometimes nodes reference nodes in other yarn files. When these nodes are opened, an empty node is created by default in the same yarn file. This is extremely annoying.
Describe the solution you'd like
We would like an option similar to what is available in the Yarn Editor that allows you to disable this automatic node generation.
Describe your use case
A massive project spread out across multiple .yarn files for organization purposes, with nodes that reference other nodes in different files.
Describe alternatives you've considered
Continuing to use the Yarn Editor.
Is your feature request related to a problem? Please describe. Our project is massive and split across several different yarn files. Sometimes nodes reference nodes in other yarn files. When these nodes are opened, an empty node is created by default in the same yarn file. This is extremely annoying.
Describe the solution you'd like We would like an option similar to what is available in the Yarn Editor that allows you to disable this automatic node generation.
Describe your use case A massive project spread out across multiple .yarn files for organization purposes, with nodes that reference other nodes in different files.
Describe alternatives you've considered Continuing to use the Yarn Editor.