Clarify why createDedicatedInputsAndOutputs is not used

Author: gosar

smithy-typescript-codegen/src/main/java/software/amazon/smithy/typescript/codegen/TypeScriptCodegenPlugin.java

@@ -56,8 +56,9 @@ public void execute(PluginContext context) {
         // Configure the director to perform some common model transforms.
         runner.performDefaultCodegenTransforms();
 
-        // TODO: How is smithy-typescript currently dealing with no input/output?
-//        runner.createDedicatedInputsAndOutputs();
+        // TODO: Not using below because it would break existing AWS SDKs. Maybe it should be configurable
+        // so generic SDKs call this by default, but AWS SDKs can opt-out of it via a setting.
+        // runner.createDedicatedInputsAndOutputs();
 
         // Run it!
         runner.run();

smithy-typescript-codegen/src/main/java/software/amazon/smithy/typescript/codegen/TypeScriptServerCodegenPlugin.java

@@ -56,8 +56,9 @@ public void execute(PluginContext context) {
         // Configure the director to perform some common model transforms.
         runner.performDefaultCodegenTransforms();
 
-        // TODO: How is smithy-typescript currently dealing with no input/output?
-//        runner.createDedicatedInputsAndOutputs();
+        // TODO: Not using below because it would break existing AWS SDKs. Maybe it should be configurable
+        // so generic SDKs call this by default, but AWS SDKs can opt-out of it via a setting.
+        // runner.createDedicatedInputsAndOutputs();
 
         // Run it!
         runner.run();