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
The Underscore.js docs have a section explaining the "OOP Style" and how chaining works. This info is not nearly as visible in the Lodash docs.
For a while I assumed Lodash didn't even support this syntax until trying it recently. Only after scrolling very carefully through the entire doc list did I notice an entry for _ under Seq which when clicking that single character started to explain that functionality. (But I still don't know what a Seq is 😝 or why it's under that heading. Maybe it stands for method chain sequence? But will newcomers know that?)
Could there possibly be a more visible heading for this content seeing as it's not just "another Lodash function" but really an entirely different way of interacting with the whole library. Perhaps something akin to the Underscore docs?
(And by the way, what does _#value mean? Shouldn't it say .value()?)
The text was updated successfully, but these errors were encountered:
The Underscore.js docs have a section explaining the "OOP Style" and how chaining works. This info is not nearly as visible in the Lodash docs.
For a while I assumed Lodash didn't even support this syntax until trying it recently. Only after scrolling very carefully through the entire doc list did I notice an entry for
_
underSeq
which when clicking that single character started to explain that functionality. (But I still don't know what aSeq
is 😝 or why it's under that heading. Maybe it stands for method chain sequence? But will newcomers know that?)Could there possibly be a more visible heading for this content seeing as it's not just "another Lodash function" but really an entirely different way of interacting with the whole library. Perhaps something akin to the Underscore docs?
(And by the way, what does
_#value
mean? Shouldn't it say.value()
?)The text was updated successfully, but these errors were encountered: