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
I've been wanting to contribute to some of your projects, and then I stumbled upon this nifty little package.
So after playing around with the API for a while I had a few different names for the feaure:
scope()/unscope()/scopeGroup()
I find this a relevant word since this feature will be used to group entries by a prefix to isolate them from other keys that might be "out of scope".
focus()/unfocus()/focusGroup()
Nice because can be "eye" related word-wise, and focusGroup is funny pun
prefix()/endPrefix()/prefixGroup()
Describes exactly what it does, but feels clunky since the naming reminds me of writing a Blade directive instead of a cache related operation.
Any of the three names I would be satisfied with, so feel free to say if you'd like focus() or prefix() instead of scope() or something entirely different.
Before writing this PR I stumbled upon #2, which describes exactly this feature but my take on it U feel like is a bit more expressive.
About
I've been wanting to contribute to some of your projects, and then I stumbled upon this nifty little package.
So after playing around with the API for a while I had a few different names for the feaure:
scope()
/unscope()
/scopeGroup()
I find this a relevant word since this feature will be used to group entries by a prefix to isolate them from other keys that might be "out of scope".
focus()
/unfocus()
/focusGroup()
Nice because can be "eye" related word-wise, and
focusGroup
is funny punprefix()
/endPrefix()
/prefixGroup()
Describes exactly what it does, but feels clunky since the naming reminds me of writing a Blade directive instead of a cache related operation.
Any of the three names I would be satisfied with, so feel free to say if you'd like
focus()
orprefix()
instead ofscope()
or something entirely different.Before writing this PR I stumbled upon #2, which describes exactly this feature but my take on it U feel like is a bit more expressive.
Feature suggestion:
Here is what I've written in the docs on my branch:
Playground
Method signatures
scope
unscope
scopeGroup
The text was updated successfully, but these errors were encountered: