[Bug]: Unable to apply different templates for operation in different versions

[live1206]

Describe the bug

We need to apply different templates for update operation in different versions as below, but complier is complaining duplication of update

  @renamedFrom(Versions.v1, "update")
  @removed(Versions.v2)
  update1 is ArmResourcePatchSync<Employee, EmployeeProperties>;

  @added(Versions.v2)
  @parameterVisibility
  update is ArmCustomPatchAsync<Employee, Employee>;

 error interface-duplicate Interface already has a member named update

Reproduction

Details

Checklist

• [X] Follow our Code of Conduct
• [X] Check that this issue is about the Azure libraries for typespec. For bug in the typespec language or core libraries file it in the TypeSpec repo
• [X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• [X] The provided reproduction is a minimal reproducible example of the bug.

[timotheeguerin]

You have to give it a different name in the old one playground

  @renamedFrom(Versions.v1, "update")
  @removed(Versions.v2)
  @sharedRoute
  updateOld is ArmResourcePatchSync<Employee, EmployeeProperties>;

  @added(Versions.v2)
  @parameterVisibility
  @sharedRoute
  update is ArmCustomPatchAsync<Employee, Employee>;

[markcowl]

As timothee showed, here is a playground showing this

[live1206]

You have to give it a different name in the old one playground

  @renamedFrom(Versions.v1, "update")
  @removed(Versions.v2)
  @sharedRoute
  updateOld is ArmResourcePatchSync<Employee, EmployeeProperties>;

  @added(Versions.v2)
  @parameterVisibility
  @sharedRoute
  update is ArmCustomPatchAsync<Employee, Employee>;

I did try to give it a different name for the old one, the key is @sharedRoute. Thanks for the help, @timotheeguerin

[tadelesh]

oh, @sharedRoute. but i do think typespec should introduce way to versioning decorator instead of using track to handle it since lots of protocol level breaking changes are from decorators.