[Bug]: [Ask]Ambiguous-symbol "nextLink" is an ambiguous name between TypeSpec.nextLink, Azure.Core.nextLink

[MaryGao]

Describe the bug

With below spec we received 1 errors with Ambiguous-symbol "nextLink" is an ambiguous name between TypeSpec.nextLink, Azure.Core.nextLink. I think this is because we both have nextLink decoration in TypeSpec and Azure.Core scope. And adding prefix could fix this issue. But I was wondering following questions regarding these decorators.

• Are the duplicated decorators expecetd? Which one is preferred to use in Azure?
• For custom paging what is the recommanded practice, typespec support vs azure core support?

playground

@pagedResult
model Bar {
  @items
  items: string[];

  @nextLink
  nextLink: url;
}

// vs

model Page<T> {
  @nextLink nextLink: url;

  @pageItems
  items: T[];
}

@list op Foo(): Page<string>;

Reproduction

NA

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[MaryGao]

Another question is if we could accept array as paged items directly for list operation? Previouly this is acceptable.

playground

[wanlwanl]

@AlitzelMendez Could you take a look at Azure/azure-sdk-tools#9554