I've seen this come up a couple times where someone has typed layers instead of layer in the property options for featuresAt or featuresIn 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 stringssomeone
:+1: I've done this many times.
:-1: rename to layers, require an array of strings as an argument. One true way.
I agree with @tmcw.
Agree with one true way, though should we continue to support the singular form, to avoid a breaking change?
Let's support an array-valued layers property only, as part of #2052 / #2224, which are already breaking changes.
cc @ansis
Most helpful comment
I agree with @tmcw.