You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the section with object but not array is used, it is incorrectly interpreted as section with array. The reason is that section renderer cannot recognize it as IDictionary, but while JObject implements both IDictionary<string, JToken> and IEnumerable. Proposed fix is by converting this special case into Dictionary of properties.
The text was updated successfully, but these errors were encountered:
Thanks very much for opening this issue. You're right it seems to be related to how we identity that the section can be iterated on and it instead tries to loop through all the members in the JObject. We have a method of filtering types we don't want the standard logic to apply which we do for both string and IDictionary.
You can override the section blacklist by using the SetSectionBlacklistTypes method on the builder however this doesn't allow you to just add to the blacklist which we've added to Stubble here: StubbleOrg/Stubble#70
With this change we can add to the extension the ability to blacklist IDictionary<string, JToken> which will make the logic work as intended
See PR #8.
If the section with object but not array is used, it is incorrectly interpreted as section with array. The reason is that section renderer cannot recognize it as IDictionary, but while JObject implements both IDictionary<string, JToken> and IEnumerable. Proposed fix is by converting this special case into Dictionary of properties.
The text was updated successfully, but these errors were encountered: