Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
When asp-if evaluates to false, the content is still generated, and suppressed after
See original GitHub issueSay we invoke a partial view such as:
<partial name="_PersonSummary" model="Model.PersonSummaryInfo" asp-if="Model.PersonSummaryInfo is not null" />
The partial view assumes that its supplied model is not null, so a null reference exception happens if it’s invoked when PersonSummaryInfo is null. A standard @if block around the <partial> prevents that, but asp-if doesn’t because the partial is still invoked.
Please close the issue if this is expected behaviour or if there’s no way around it other than sticking with an @if block, or changing the partial to cope with a null model.
Issue Analytics
- State:
- Created 9 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@DamianEdwards Works a treat thanks.
Updated the tag helpers defined in my own codebase to set the Order and use the SuppressedByAspIf extension method in line with this change. So it’s handy you made that public 😄
OK it should up shortly at https://www.nuget.org/packages/TagHelperPack/0.9.0-pre-20221214.35