Missing interface in non-modular code generation

[alfie80]

Hi Team,

I have below model definitions in Typespec and I found the the interfaces CatDef and DefaultPets will be missed in the generated codes. However, switching to modular mode (setting is-modular-library to true), the interfaces are generated.

model DefaultPets {
    catList?: CatDef[] = #[
        #{
            catType: "American Shorthair"
        }
    ];
}

model PetSettings {
    petList?: {
      cat?: DefaultPets.catList;
    },
}

model CatDef {
  catType: string;
}

The problem seems relates to cat?: DefaultPets.catList in model PetSettings. After changing it to below, the interface CatDef can be generated.

model PetSettings {
    petList?: {
      cat?: CatDef[] = #[
        #{
            catType: "American Shorthair"
         }
      ];
    },
}

Here is my emitter setting in tspconfig.yaml:

emit:
  - '@azure-tools/typespec-ts'
options:
  "@azure-tools/typespec-ts":
    azure-sdk-for-js: false
    enable-operation-group: true
    include-shortcuts: true
    is-modular-library: false
    ignore-property-name-normalize: true

[MaryGao]

It seems there is bug in RLC for referenced model generation. @alfie80 May I know why we generate RLC libraries(that is is-modular-library: false) in your case? I am asking because RLC is in maintaince mode and any issues reported may be handled as low priority. Could we switch to Modular(that is is-modular-library) then?

[alfie80]

Thanks @MaryGao for your reply. Does that mean the RLC will not be supported any more in future? Do you know when? We now generate RLC as our SDK's low level codes. Is the Modular our only choice? Thanks.