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
A suggested improvement for entrymatcher~ would be the ability to query from a starting column and for a given range to making for tidier messaging if you're just trying to find the nearest equal match across a normalized/standardized range of values.
So something like column1 20 % 1. [$1 $2 $3 etc...] to query starting on column one, for two columns, followed by the list of values for the query.
Instead of having column1 % 1. $1 column2 % 1. $2 column3 % 1. $3, etc...
Or an even fancier-pants version would be to have matchers messages be "sticky" or @attributes-y where you can specify the type of query you want (e.g. column1 20 % 1. ) and then just send the values to be queried.
The text was updated successfully, but these errors were encountered:
A suggested improvement for
entrymatcher~
would be the ability to query from a starting column and for a given range to making for tidier messaging if you're just trying to find the nearest equal match across a normalized/standardized range of values.So something like
column1 20 % 1. [$1 $2 $3 etc...]
to query starting on column one, for two columns, followed by the list of values for the query.Instead of having
column1 % 1. $1 column2 % 1. $2 column3 % 1. $3, etc...
Or an even fancier-pants version would be to have
matchers
messages be "sticky" or@attributes
-y where you can specify the type of query you want (e.g.column1 20 % 1.
) and then just send the values to be queried.The text was updated successfully, but these errors were encountered: