Fix visibility conflict with base models (#3049)

fix #2922
fix #3048(dup)

.chronus/changes/fix-visibility-conflict-base-model-2024-2-25-15-48-50.md

@@ -0,0 +1,8 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: fix
+packages:
+  - "@typespec/openapi3"
+---
+
+Fix visibility naming conflict when a model used with `extends` was used in different visibility.

packages/openapi3/src/visibility-usage.ts

@@ -171,6 +171,9 @@ function navigateReferencedTypes(
     case "Model":
       callback(type, usage);
       navigateIterable(type.properties, usage, callback, visited);
+      if (type.baseModel) {
+        navigateReferencedTypes(type.baseModel, usage, callback, visited);
+      }
       navigateIterable(type.derivedModels, usage, callback, visited);
       if (type.indexer) {
         if (type.indexer.key.name === "integer") {

packages/openapi3/test/metadata.test.ts

@@ -1130,4 +1130,27 @@ describe("openapi3: metadata", () => {
       },
     });
   });
+
+  it("base models used in different visibility gets distinct names", async () => {
+    const res = await openApiFor(`
+      model Widget {
+        @visibility("read", "update")
+        @path
+        id: string;
+      
+        weight: int32;
+      }
+      
+      model CreatedWidget extends Widget {}
+      
+      @post op create(widget: Widget): CreatedWidget;
+    `);
+
+    deepStrictEqual(Object.keys(res.components.schemas), [
+      "CreatedWidget",
+      "CreatedWidgetCreate",
+      "Widget",
+      "WidgetCreate",
+    ]);
+  });
 });