Closed MikeTraceur closed 2 months ago
IMHO not fixing this is the wrong decision. Postponing it for a major release due to a potentially breaking change, OK. But not fixing it at all?
Why would you think so? It doesn't change functionality... It's a harmless typo in an enum constant name.
Well, it's clearly written wrong and it feels sloppy to me when I see such things in code. I mean correcting it might break some users code but it's so easy to fix anyway. But, your library, your decision of course.
Hi Mike,
Thanks, but since the enum is public and exposed, this is a potentially breaking change and as such I'm not really willing to merge it.