OpenAPI applies read visibility to unreachable types

[mikekistler]

The docs for @withVisibility show this example

model Dog {
  @visibility("read") id: int32;
  @visibility("create", "update") secretName: string;
  name: string;
}

// The spread operator will copy all the properties of Dog into DogRead,
// and @withVisibility will then remove those that are not visible with
// create or update visibility.
//
// In this case, the id property is removed, and the name and secretName
// properties are kept.
@withVisibility("create", "update")
model DogCreateOrUpdate {
  ...Dog;
}

but the actual behavior as shown in the playground does not match the description in the doc.

Playground Link

Note that secretName does not appear in either Dog or DogCreateOrUpdate.

[bterlson]

I believe the root cause in this particular case is that we are applying read visibility to models that aren't used in an operation.

import "@typespec/http";

using TypeSpec.Http;

model DogCreateOrUpdate {
  @visibility("read") id: int32;
  @visibility("create") secretName: string;
}

Playground

I would expect both fields to be present in this case.

[timotheeguerin]

Keeping this issue for fixing withVisibilities and opened a new one about openapi3 handling of unreachable types #2571