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
We started with the *ByKey commands, where "by" makes sense, and added the *ByPath commands later. Since they took the same arguments, it felt like it made sense to keep the same "by" preposition, instead of the more natural "at".
What's the expected behavior?
But with the removal of the key-based commands of #2858, and our existing use of "at" for range commands, it makes more sense to have *AtPath and *AtRange together. (And also *AtPoint in the future.)
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Improvement.
What's the current behavior?
We started with the
*ByKey
commands, where "by" makes sense, and added the*ByPath
commands later. Since they took the same arguments, it felt like it made sense to keep the same "by" preposition, instead of the more natural "at".What's the expected behavior?
But with the removal of the key-based commands of #2858, and our existing use of "at" for range commands, it makes more sense to have
*AtPath
and*AtRange
together. (And also*AtPoint
in the future.)The text was updated successfully, but these errors were encountered: