Inifinite loop during model binding when using [ModelBinder] attribute












1















I initially posted this issue to GitHub here: https://github.com/aspnet/Mvc/issues/8723



There's a GitHub repository with a repro of the problem here:
https://github.com/Costo/aspnetcore-binding-bug



I'm using ASP.NET Core 2.2 Preview 3.



When using a custom model binder (with the [ModelBinder] attribute) on properties of an array of "child" models, the model binding phase of the request goes into an infinite loop. See this screenshot:



Model binding looping infinitely



The custom model binder works well if used on top level model properties, but I'd like to understand why it doesn't work when used in an array of child models. Any help with this would be appreciated.



Thank you !





Here's the code of the model, controller, view and custom binder:



The Model:



public class TestModel
{
public TestInnerModel InnerModels { get; set; } = new TestInnerModel[0];

[ModelBinder(BinderType = typeof(NumberModelBinder))]
public decimal TopLevelRate { get; set; }
}

public class TestInnerModel
{
public TestInnerModel()
{
}

[ModelBinder(BinderType = typeof(NumberModelBinder))]
public decimal Rate { get; set; }
}


The custom model binder (intentionally simplified to do nothing special):



public class NumberModelBinder : IModelBinder
{
private readonly NumberStyles _supportedStyles = NumberStyles.Float | NumberStyles.AllowThousands;
private DecimalModelBinder _innerBinder;

public NumberModelBinder(ILoggerFactory loggerFactory)
{
_innerBinder = new DecimalModelBinder(_supportedStyles, loggerFactory);
}

/// <inheritdoc />
public Task BindModelAsync(ModelBindingContext bindingContext)
{
return _innerBinder.BindModelAsync(bindingContext);
}
}


The controller:



public class HomeController : Controller
{
public IActionResult Index()
{
return View(new TestModel
{
TopLevelRate = 20m,
InnerModels = new TestInnerModel
{
new TestInnerModel { Rate = 2.0m },
new TestInnerModel { Rate = 0.2m }
}
});
}

[HttpPost]
public IActionResult Index(TestModel model)
{
return Ok();
}
}


The Razor view:



@model TestModel;

<form asp-controller="Home" asp-action="Index" method="post" role="form">
<div>
<input asp-for="@Model.TopLevelRate" type="number" min="0" step=".01" />

</div>
<div>
@for (var i = 0; i < Model.InnerModels.Length; i++)
{
<input asp-for="@Model.InnerModels[i].Rate" type="number" min="0" step=".01" />
}
</div>

<input type="submit" value="Go" />
</form>









share|improve this question





























    1















    I initially posted this issue to GitHub here: https://github.com/aspnet/Mvc/issues/8723



    There's a GitHub repository with a repro of the problem here:
    https://github.com/Costo/aspnetcore-binding-bug



    I'm using ASP.NET Core 2.2 Preview 3.



    When using a custom model binder (with the [ModelBinder] attribute) on properties of an array of "child" models, the model binding phase of the request goes into an infinite loop. See this screenshot:



    Model binding looping infinitely



    The custom model binder works well if used on top level model properties, but I'd like to understand why it doesn't work when used in an array of child models. Any help with this would be appreciated.



    Thank you !





    Here's the code of the model, controller, view and custom binder:



    The Model:



    public class TestModel
    {
    public TestInnerModel InnerModels { get; set; } = new TestInnerModel[0];

    [ModelBinder(BinderType = typeof(NumberModelBinder))]
    public decimal TopLevelRate { get; set; }
    }

    public class TestInnerModel
    {
    public TestInnerModel()
    {
    }

    [ModelBinder(BinderType = typeof(NumberModelBinder))]
    public decimal Rate { get; set; }
    }


    The custom model binder (intentionally simplified to do nothing special):



    public class NumberModelBinder : IModelBinder
    {
    private readonly NumberStyles _supportedStyles = NumberStyles.Float | NumberStyles.AllowThousands;
    private DecimalModelBinder _innerBinder;

    public NumberModelBinder(ILoggerFactory loggerFactory)
    {
    _innerBinder = new DecimalModelBinder(_supportedStyles, loggerFactory);
    }

    /// <inheritdoc />
    public Task BindModelAsync(ModelBindingContext bindingContext)
    {
    return _innerBinder.BindModelAsync(bindingContext);
    }
    }


    The controller:



    public class HomeController : Controller
    {
    public IActionResult Index()
    {
    return View(new TestModel
    {
    TopLevelRate = 20m,
    InnerModels = new TestInnerModel
    {
    new TestInnerModel { Rate = 2.0m },
    new TestInnerModel { Rate = 0.2m }
    }
    });
    }

    [HttpPost]
    public IActionResult Index(TestModel model)
    {
    return Ok();
    }
    }


    The Razor view:



    @model TestModel;

    <form asp-controller="Home" asp-action="Index" method="post" role="form">
    <div>
    <input asp-for="@Model.TopLevelRate" type="number" min="0" step=".01" />

    </div>
    <div>
    @for (var i = 0; i < Model.InnerModels.Length; i++)
    {
    <input asp-for="@Model.InnerModels[i].Rate" type="number" min="0" step=".01" />
    }
    </div>

    <input type="submit" value="Go" />
    </form>









    share|improve this question



























      1












      1








      1


      2






      I initially posted this issue to GitHub here: https://github.com/aspnet/Mvc/issues/8723



      There's a GitHub repository with a repro of the problem here:
      https://github.com/Costo/aspnetcore-binding-bug



      I'm using ASP.NET Core 2.2 Preview 3.



      When using a custom model binder (with the [ModelBinder] attribute) on properties of an array of "child" models, the model binding phase of the request goes into an infinite loop. See this screenshot:



      Model binding looping infinitely



      The custom model binder works well if used on top level model properties, but I'd like to understand why it doesn't work when used in an array of child models. Any help with this would be appreciated.



      Thank you !





      Here's the code of the model, controller, view and custom binder:



      The Model:



      public class TestModel
      {
      public TestInnerModel InnerModels { get; set; } = new TestInnerModel[0];

      [ModelBinder(BinderType = typeof(NumberModelBinder))]
      public decimal TopLevelRate { get; set; }
      }

      public class TestInnerModel
      {
      public TestInnerModel()
      {
      }

      [ModelBinder(BinderType = typeof(NumberModelBinder))]
      public decimal Rate { get; set; }
      }


      The custom model binder (intentionally simplified to do nothing special):



      public class NumberModelBinder : IModelBinder
      {
      private readonly NumberStyles _supportedStyles = NumberStyles.Float | NumberStyles.AllowThousands;
      private DecimalModelBinder _innerBinder;

      public NumberModelBinder(ILoggerFactory loggerFactory)
      {
      _innerBinder = new DecimalModelBinder(_supportedStyles, loggerFactory);
      }

      /// <inheritdoc />
      public Task BindModelAsync(ModelBindingContext bindingContext)
      {
      return _innerBinder.BindModelAsync(bindingContext);
      }
      }


      The controller:



      public class HomeController : Controller
      {
      public IActionResult Index()
      {
      return View(new TestModel
      {
      TopLevelRate = 20m,
      InnerModels = new TestInnerModel
      {
      new TestInnerModel { Rate = 2.0m },
      new TestInnerModel { Rate = 0.2m }
      }
      });
      }

      [HttpPost]
      public IActionResult Index(TestModel model)
      {
      return Ok();
      }
      }


      The Razor view:



      @model TestModel;

      <form asp-controller="Home" asp-action="Index" method="post" role="form">
      <div>
      <input asp-for="@Model.TopLevelRate" type="number" min="0" step=".01" />

      </div>
      <div>
      @for (var i = 0; i < Model.InnerModels.Length; i++)
      {
      <input asp-for="@Model.InnerModels[i].Rate" type="number" min="0" step=".01" />
      }
      </div>

      <input type="submit" value="Go" />
      </form>









      share|improve this question
















      I initially posted this issue to GitHub here: https://github.com/aspnet/Mvc/issues/8723



      There's a GitHub repository with a repro of the problem here:
      https://github.com/Costo/aspnetcore-binding-bug



      I'm using ASP.NET Core 2.2 Preview 3.



      When using a custom model binder (with the [ModelBinder] attribute) on properties of an array of "child" models, the model binding phase of the request goes into an infinite loop. See this screenshot:



      Model binding looping infinitely



      The custom model binder works well if used on top level model properties, but I'd like to understand why it doesn't work when used in an array of child models. Any help with this would be appreciated.



      Thank you !





      Here's the code of the model, controller, view and custom binder:



      The Model:



      public class TestModel
      {
      public TestInnerModel InnerModels { get; set; } = new TestInnerModel[0];

      [ModelBinder(BinderType = typeof(NumberModelBinder))]
      public decimal TopLevelRate { get; set; }
      }

      public class TestInnerModel
      {
      public TestInnerModel()
      {
      }

      [ModelBinder(BinderType = typeof(NumberModelBinder))]
      public decimal Rate { get; set; }
      }


      The custom model binder (intentionally simplified to do nothing special):



      public class NumberModelBinder : IModelBinder
      {
      private readonly NumberStyles _supportedStyles = NumberStyles.Float | NumberStyles.AllowThousands;
      private DecimalModelBinder _innerBinder;

      public NumberModelBinder(ILoggerFactory loggerFactory)
      {
      _innerBinder = new DecimalModelBinder(_supportedStyles, loggerFactory);
      }

      /// <inheritdoc />
      public Task BindModelAsync(ModelBindingContext bindingContext)
      {
      return _innerBinder.BindModelAsync(bindingContext);
      }
      }


      The controller:



      public class HomeController : Controller
      {
      public IActionResult Index()
      {
      return View(new TestModel
      {
      TopLevelRate = 20m,
      InnerModels = new TestInnerModel
      {
      new TestInnerModel { Rate = 2.0m },
      new TestInnerModel { Rate = 0.2m }
      }
      });
      }

      [HttpPost]
      public IActionResult Index(TestModel model)
      {
      return Ok();
      }
      }


      The Razor view:



      @model TestModel;

      <form asp-controller="Home" asp-action="Index" method="post" role="form">
      <div>
      <input asp-for="@Model.TopLevelRate" type="number" min="0" step=".01" />

      </div>
      <div>
      @for (var i = 0; i < Model.InnerModels.Length; i++)
      {
      <input asp-for="@Model.InnerModels[i].Rate" type="number" min="0" step=".01" />
      }
      </div>

      <input type="submit" value="Go" />
      </form>






      asp.net-core-mvc






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '18 at 15:24







      Costo

















      asked Nov 14 '18 at 15:17









      CostoCosto

      3,42072835




      3,42072835
























          1 Answer
          1






          active

          oldest

          votes


















          0














          A solution was posted to the GitHub issue:




          @Costo The problem is you're not informing the model binding system that the binder uses value providers. The ComplexTypeModelBinder always believes data is available for the next TestInnerModel instance and the outermost binder (CollectionModelBinder) keeps going -- forever. To fix this,




          [MyModelBinder]
          public decimal Rate { get; set; }

          private class MyModelBinderAttribute : ModelBinderAttribute
          {
          public MyModelBinderAttribute()
          : base(typeof(NumberModelBinder))
          {
          BindingSource = BindingSource.Form;
          }
          }



          Put another way, the BindingSource.Custom default [ModelBinder] uses isn't correct in this scenario. Fortunately custom model binders on properties of POCO types in containers should be one of the very few cases where this matters.







          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53303414%2finifinite-loop-during-model-binding-when-using-modelbinder-attribute%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            A solution was posted to the GitHub issue:




            @Costo The problem is you're not informing the model binding system that the binder uses value providers. The ComplexTypeModelBinder always believes data is available for the next TestInnerModel instance and the outermost binder (CollectionModelBinder) keeps going -- forever. To fix this,




            [MyModelBinder]
            public decimal Rate { get; set; }

            private class MyModelBinderAttribute : ModelBinderAttribute
            {
            public MyModelBinderAttribute()
            : base(typeof(NumberModelBinder))
            {
            BindingSource = BindingSource.Form;
            }
            }



            Put another way, the BindingSource.Custom default [ModelBinder] uses isn't correct in this scenario. Fortunately custom model binders on properties of POCO types in containers should be one of the very few cases where this matters.







            share|improve this answer




























              0














              A solution was posted to the GitHub issue:




              @Costo The problem is you're not informing the model binding system that the binder uses value providers. The ComplexTypeModelBinder always believes data is available for the next TestInnerModel instance and the outermost binder (CollectionModelBinder) keeps going -- forever. To fix this,




              [MyModelBinder]
              public decimal Rate { get; set; }

              private class MyModelBinderAttribute : ModelBinderAttribute
              {
              public MyModelBinderAttribute()
              : base(typeof(NumberModelBinder))
              {
              BindingSource = BindingSource.Form;
              }
              }



              Put another way, the BindingSource.Custom default [ModelBinder] uses isn't correct in this scenario. Fortunately custom model binders on properties of POCO types in containers should be one of the very few cases where this matters.







              share|improve this answer


























                0












                0








                0







                A solution was posted to the GitHub issue:




                @Costo The problem is you're not informing the model binding system that the binder uses value providers. The ComplexTypeModelBinder always believes data is available for the next TestInnerModel instance and the outermost binder (CollectionModelBinder) keeps going -- forever. To fix this,




                [MyModelBinder]
                public decimal Rate { get; set; }

                private class MyModelBinderAttribute : ModelBinderAttribute
                {
                public MyModelBinderAttribute()
                : base(typeof(NumberModelBinder))
                {
                BindingSource = BindingSource.Form;
                }
                }



                Put another way, the BindingSource.Custom default [ModelBinder] uses isn't correct in this scenario. Fortunately custom model binders on properties of POCO types in containers should be one of the very few cases where this matters.







                share|improve this answer













                A solution was posted to the GitHub issue:




                @Costo The problem is you're not informing the model binding system that the binder uses value providers. The ComplexTypeModelBinder always believes data is available for the next TestInnerModel instance and the outermost binder (CollectionModelBinder) keeps going -- forever. To fix this,




                [MyModelBinder]
                public decimal Rate { get; set; }

                private class MyModelBinderAttribute : ModelBinderAttribute
                {
                public MyModelBinderAttribute()
                : base(typeof(NumberModelBinder))
                {
                BindingSource = BindingSource.Form;
                }
                }



                Put another way, the BindingSource.Custom default [ModelBinder] uses isn't correct in this scenario. Fortunately custom model binders on properties of POCO types in containers should be one of the very few cases where this matters.








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 14 '18 at 15:59









                CostoCosto

                3,42072835




                3,42072835
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53303414%2finifinite-loop-during-model-binding-when-using-modelbinder-attribute%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Xamarin.iOS Cant Deploy on Iphone

                    Glorious Revolution

                    Dulmage-Mendelsohn matrix decomposition in Python