Ok I reconsidered the issue(#17) and changed my mind.
When I think which is simpler and which is more advanced, obviously "common object" is simpler and the current "expect/actual object" is more advanced/complex.
So I thought the new "common object" should be the default behavior, and the current "expect/actual object" should be an advanced option.
BuildKonfig now generates
common single object if there's no targetConfigs defined.
expect object in commonMain, and actual object in each target sourceSets if there's targetConfigs.(the current behavior)
17
Ok I reconsidered the issue(#17) and changed my mind.
When I think which is simpler and which is more advanced, obviously "common object" is simpler and the current "expect/actual object" is more advanced/complex.
So I thought the new "common object" should be the default behavior, and the current "expect/actual object" should be an advanced option.
BuildKonfig now generates
targetConfigsdefined.expectobject in commonMain, andactualobject in each target sourceSets if there'stargetConfigs.(the current behavior)