-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename layer
option to layers
for featuresIn/At requests
#2230
Labels
Comments
👍 I've done this many times. |
👎 rename to layers, require an array of strings as an argument. One true way. |
layers
option for featuresIn/At requestslayer
option to layers
for featuresIn/At requests
I agree with @tmcw. |
Agree with |
ansis
added a commit
that referenced
this issue
Mar 15, 2016
and accept only an array of strings. fix #2230
ansis
added a commit
that referenced
this issue
Mar 15, 2016
and accept only an array of strings. fix #2230
ansis
added a commit
that referenced
this issue
Mar 16, 2016
and accept only an array of strings. fix #2230
ansis
added a commit
that referenced
this issue
Mar 16, 2016
and accept only an array of strings. fix #2230
ansis
added a commit
that referenced
this issue
Mar 17, 2016
and accept only an array of strings. fix #2230
ansis
added a commit
that referenced
this issue
Mar 21, 2016
and accept only an array of strings. fix #2230
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've seen this come up a couple times where someone has typed
layers
instead oflayer
in the property options forfeaturesAt
orfeaturesIn
requests. If the typo is not caught the effect is elusive (appears to sort of work as the layer you want is captured in the request but buggy as it captures others)Propose:
layer
continues to accept a single string value or an array of stringslayers
accepts an array of stringsThe text was updated successfully, but these errors were encountered: