Support an option to generate code as one file per namespace and address huge performance problem. #426
Description
We have a HUGE metadata file and generating a single file is no good nor is one file per entity (already supported).
Describe the solution you'd like
Add another option to do this.
Describe alternatives you've considered
Generating one file per entity and letting other developers grab just the files they need but there are thousands if files for them to wade through.
Additional context
Yes, the extension (n our case) generates 57 pages of entities that we can scroll through and select but we cannot select because the next page is never populated, this is a bug and adding the per-namespace option would be better anyway, we'd still get a lot of files but nowhere near as many as one per entity.
Also one file per entity takes a LONG time (its been generating code for 90 minutes already and has generated 2,386 files so far) to generate all the files, we have over 2,200 files generated and I think there's a perf hotspot too when there are this many files as the rate of file generation seems to steadily fall as it progresses.
Look:
You can see it has generated just 25 files in the past 22 minutes, that seems seriously slow.
Compare that rate to how it started:
In fact it generated over 200 files at 6:58, within the space of one minute.
See here for details and additional context.