[BUG] RefitStubs.g.cs is empty

[wahmedswl]

Describe the bug

RefitStubs.g.cs generated is empty, checked it in obj folder

// <auto-generated />
using System;
using System.Net.Http;
using System.Collections.Generic;

/* ******** Hey You! *********
 *
 * This is a generated file, and gets rewritten every time you build the
 * project. If you want to edit it, you need to edit the mustache template
 * in the Refit package */

#pragma warning disable
namespace TwilioApi.Model.RefitInternalGenerated
{
    [global::System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverage]
    [AttributeUsage (AttributeTargets.Class | AttributeTargets.Struct | AttributeTargets.Enum | AttributeTargets.Constructor | AttributeTargets.Method | AttributeTargets.Property | AttributeTargets.Field | AttributeTargets.Event | AttributeTargets.Interface | AttributeTargets.Delegate)]
    sealed class PreserveAttribute : Attribute
    {

        //
        // Fields
        //
        public bool AllMembers;

        public bool Conditional;
    }
}
#pragma warning restore

I have following interface defined with Refit

using Refit;
using SequelMed.Core;
using System.Collections.Generic;
using System.Threading.Tasks;
using Twilio.Rest.Studio.V1.Flow;

namespace TwilioApi.Model
{
    public interface IReminderClient
    {
        [Post("/" + Routes.PF_REMINDER + "/" + Routes.REMINDER_SEND)]
        Task<Envelope<ExecutionResource>> Send(ReminderRequest payload);

        [Post("/" + Routes.PF_REMINDER + "/" + Routes.REMINDER_RESPONSE)]
        Task<Envelope<string>> Response(ReminderRequest payload);

        [Post("/" + Routes.PF_REMINDER + "/" + Routes.REMINDER_PULL)]
        Task<Envelope<List<ReminderResponse>>> Pull(ReminderRequest payload);

        [Post("/" + Routes.PF_REMINDER + "/" + Routes.REMINDER_ACK)]
        Task<Envelope<string>> Acknowledge(ReminderRequest payload);
    }
}

Steps To Reproduce

Expected behavior

Screenshots

Environment

• OS: Windows, .Net461
• Version
• Device:

Additional context

[clairernovotny]

Have you tried it without the constants?

[wahmedswl]

@onovotny thanks for your reply. Yes, it worked without Constants. So, is this the way to go and Constants won't work?

[clairernovotny]

Correct, see the main issue here:
#602

Closing as dup of #602

[jamiehowarth0]

I added comments on #263, basically constants aren't supported as default values in any optional params, up to and including C# 8, I don't see why we should support them in param values, as it'll involve Roslyn work which would require a refactor too substantial to warrant as a feature improvement.