API change suggestion on set(key, value[, clobber=true]) about caseless HOT 3 OPEN

It just feels a little weird to have an options object when there is only one option. I'm trying to think of another case where we might need an option though.

from caseless.

@mikeal while I agree that it feels weird I think it is a positive change in terms of code readability. I, as most developers, read docs when I'm trying to use a certain feature, but when reading someone else's code I usually guess by the API what the method is doing.
So, in this particular case, I would expect a key, value params in a setter method, but a third param as boolean is not intuitive at all.

So, just my two cents, feel free to close this issue if you think it is useless.

Best,
Max

from caseless.

hrm... i think you're right, i just need to think about the best way to do this without breaking API or killing performance.

from caseless.