There are parts of maslow.yaml that must be available at startup (pin assignments, etc) and parts that can be loaded later (frame details)
if they get split into different files, problems with setting frame details won't affect the more critical things like pin assignments (and we can even rename the one with the pin assignments back to fluidnc.yaml, eliminating one conflict with upstream)
I think having them separate would make it less likely that the critical data will get corrupted.
I think it will also be a step towards supporting multiple frame sizes by having a file per frame and picking which one to use.
There are parts of maslow.yaml that must be available at startup (pin assignments, etc) and parts that can be loaded later (frame details)
if they get split into different files, problems with setting frame details won't affect the more critical things like pin assignments (and we can even rename the one with the pin assignments back to fluidnc.yaml, eliminating one conflict with upstream)
I think having them separate would make it less likely that the critical data will get corrupted.
I think it will also be a step towards supporting multiple frame sizes by having a file per frame and picking which one to use.