Remove core-paging dependency in RLC#2785
Conversation
|
|
||
| // @public | ||
| export type SupportedLanguagesOutput = Paged<SupportedLanguageOutput>; | ||
| export interface SupportedLanguagesOutput { |
There was a problem hiding this comment.
@joheredi @qiaozha I prefer to remove the Paged interface and directly generate paged model type as TypeSpec defined. Let me know if you have any concern!
The main reason is it would be better aligned with generating with TypeSpec defined, considering Paged interface would limit the model to have two properties(value & nextLink) so service team want to have additional properties returned or some other strucuture with paging models, this would be impossible to include them and you could see an example here. Also in TS side, we would produce more direct and simpler interface without Paged interface.
Pls note in Modular this model is generated as internal model and it is also without Paged referred. Also I believe this is not a breaking for RLC because the model shape is the same.
fixes #2780