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
It seems like we end up writing this a lot, and the most common use case is probably fetching the first match
{ $ref: 'dom.query!.whatever', i:0 }
So let's add dom.first! that automatically resolves to the first match, rather than to a nodelist of 1 item. It can take advantage of any selector-specific optimizations, such as :first, too.
As a nice parallel, let's add dom.all! which will be a synonym for dom.query! ... and maybe we should deprecate dom.query!
The text was updated successfully, but these errors were encountered:
It seems like we end up writing this a lot, and the most common use case is probably fetching the first match
{ $ref: 'dom.query!.whatever', i:0 }
So let's add
dom.first!
that automatically resolves to the first match, rather than to a nodelist of 1 item. It can take advantage of any selector-specific optimizations, such as:first
, too.As a nice parallel, let's add
dom.all!
which will be a synonym fordom.query!
... and maybe we should deprecatedom.query!
The text was updated successfully, but these errors were encountered: