Generating synchronous methods and generating response classes generates invalid code

It seems that when selecting to generate sync methods along with response classes (/WrapResponses:true /GenerateSyncMethods:true) then the signature of the sync methods are wrong. The code simply does not build.

Example of some generated code (note that apart from the Task the async and sync method differ in wrapping with SwaggerResponse). Note that since the sync method simply uses the async method this will not build:

        /// <param name="tags">tags to filter by</param>
        /// <param name="limit">maximum number of results to return</param>
        /// <returns>pet response</returns>
        /// <exception cref="SwaggerException">A server side error occurred.</exception>
        public System.Collections.ObjectModel.ObservableCollection<Pet> FindPets(System.Collections.Generic.IEnumerable<string> tags, int? limit)
        {
            return System.Threading.Tasks.Task.Run(async () => await FindPetsAsync(tags, limit, System.Threading.CancellationToken.None)).GetAwaiter().GetResult();
        }
    
        /// <param name="tags">tags to filter by</param>
        /// <param name="limit">maximum number of results to return</param>
        /// <returns>pet response</returns>
        /// <exception cref="SwaggerException">A server side error occurred.</exception>
        /// <param name="cancellationToken">A cancellation token that can be used by other objects or threads to receive notice of cancellation.</param>
        public async System.Threading.Tasks.Task<SwaggerResponse<System.Collections.ObjectModel.ObservableCollection<Pet>>> FindPetsAsync(System.Collections.Generic.IEnumerable<string> tags, int? limit, System.Threading.CancellationToken cancellationToken)
        {

Example files: ErrorExample.zip

[RicoSuter]

Should be fixed in the next version 😃

[elemarios]

Hello @RicoSuter . The bug still continue even with last version of NswagStudio(12.0.18.0) , I was wondering if you’d had a chance to replicate it. I noticed this bug still as Opened. Do I need to log a new bug?