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
If someone gives me the go-ahead, I'll implement it.
Pattern must start with three or more non-dynamic characters followed by a space, e.g. "lodash ". This'll be used to speed up look-up time, by not executing the expression until a match is likely
The text was updated successfully, but these errors were encountered:
Non-perfect-matching factoids already show all matching factoids - wouldn't this risk reducing a near-infinite namespace to existing keys plus a few cleverly crafter regexes?
Okay, here's an alternate suggestion with that in mind.
<USER> !!learn lodash {{0}} = _.{{0}} http://devdocs.io/lodash/index#{{0}}
<USER> !! lodash throttle
<bot> USER: _.throttle http://devdocs.io/lodash/index#throttle
<USER> !! lodash map
<bot> USER: _.map http://devdocs.io/lodash/index#map
<USER> !lodash
<bot> USER: the default lodash factoid or the usual help prompt
Up to {{2}} may be used (not sure if that's even needed); it's restricted to a new !! namespace (which could still technically collide with !learn ! foo = something, but good enough).
@ljharb, still don't like it, or are there any outstanding problems with this?
Certainly if you're making a new namespace, there's no collision issue. My next question is, what use case is this solving? I can already do !g lodash throttle which links me to the docs, for example.
These would be semi-dynamic factoids. A simple example:
If someone gives me the go-ahead, I'll implement it.
Pattern must start with three or more non-dynamic characters followed by a space, e.g.
"lodash "
. This'll be used to speed up look-up time, by not executing the expression until a match is likelyThe text was updated successfully, but these errors were encountered: