CamelCase vs UPPER_CASE about enums HOT 5 CLOSED

Hey, thanks for bringing this up.

I'd like to support all of these cases with sane defaults. So probably something like:

UPPERCASE_SNAKE_CASE => 'Uppercase snake case'
PascalCase => 'Pascal case'

The option values would remain the same as the case names (for pure enums, without a backing value) so that you can use fromName().

from enums.

Ah that makes sense. I think with the changes I made here, all logic should be 1:1 consistent for both UPPER_SNAKE_CASE and PascalCase enum cases, so now the only remaining step would be to make the README consistent with the more standard syntax?

from enums.

See the linked commit and let me know if that's how you'd intuitively expect it to behave (I included tests for both backed enums and pure enums). If it looks fine I'll tag a release, thanks!

from enums.

Oops accidentally overrode the test for pure PascalCase enum when I was adding the test for the backed enum.

Fixed here 61ba793

from enums.

I think my main point was that it could be useful to have
https://github.com/archtechx/enums?tab=readme-ov-file#usage
in line with the standard recommendation for it from PHP side using CamelCase
https://www.php.net/manual/en/language.types.enumerations.php

For people to use that mainly, and having upper case as optional thing, but not what usually would be used.

from enums.