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
Could hx-target extended selector syntax (with closest, find, etc) be exposed as part of the public API? It would help with writing extensions, as correctly splitting sub-selectors by commas isn't trivial.
So htmx.splitExtendedSelector("this, closest input") would produce [["this"], ["closest", "input"]].
Another option would be changing the APIs of htmx.find and htmx.findAll methods to accept the extended selector, though I'm not sure it would cover all possible cases of using the splitter.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Could
hx-target
extended selector syntax (withclosest
,find
, etc) be exposed as part of the public API? It would help with writing extensions, as correctly splitting sub-selectors by commas isn't trivial.So
htmx.splitExtendedSelector("this, closest input")
would produce[["this"], ["closest", "input"]]
.Another option would be changing the APIs of
htmx.find
andhtmx.findAll
methods to accept the extended selector, though I'm not sure it would cover all possible cases of using the splitter.Beta Was this translation helpful? Give feedback.
All reactions