Error: There are multiple operations defined for 'get: <path>' about autorest HOT 5 CLOSED

from the place where this error is emitted

         // we're attempting to put another operation at the same path/method
        // where there is one already.
        // This is likely a case where a multi-api-version file is trying to
        // go thru the composer, and this is not allowed.
        throw new Error(
          `There are multiple operations defined for \n  '${key}: ${metadata.path}'.\n\n  You are probably trying to use an input with multiple API versions with an autorest V2 generator, and that will not work. `,
        );

autorest is basically just a pipeline runner. It provides all those plugins where a few are those old legacy one(including this new composer. I have no idea why you still be calling this here.

The duplicate operation is also something I am just confused it would ever work. The only things that I can see autorest was kinda design to work with is if you loaded different version of the same api but that's something we never actually did.
If you pass those spec through the m4 pipeline(generate SDK) it also fails later complaining about some duplication. TO me this just seems like this spec shouldn't be keeping those dup operations.

The previous bug I fixed was bad in the sense that it was just crashing with a meaningless message and that's not something we should do.

from autorest.

This one looks expected to me

from autorest.

This one looks expected to me

Are you saying it's expected that autorest fails on duplicate paths, and fix #4896 was just to convert the failure from a crash to a better error message? Or did the spec have multiple issues, and fixing #4896 fixed one issue which just exposed the next issue?

from autorest.

So digging into that, it might be getting there because of autorest deciding to run the legacy pipeline by default. Maybe we could not do that anymore(though I am worried this will break existing flow) so maybe have a flag.

However my last point still stand. Even though the linter flow might not complain about that it would still fail later.

from autorest.

To me this just seems like this spec shouldn't be keeping those dup operations.

I think this was a temporary bug in the spec -- it's since been updated to remove the dup operations.

Closing for now, will re-open if this becomes a recurring problem.

from autorest.