Is it expected to allow saving invalid Enum values? #330
Unanswered
serious-angel
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear Developers,
Thank you for the marvel!
Let's, for example, have the following setting:
When we set the setting the first time, it passes a wrong Enum:
If we trace the call during a run, the type is delivered correctly from the DocBlock on:
laravel-settings/src/Support/PropertyReflector.php
Line 71 in fd3db34
Yet, later, we cannot get nor set the setting property (new Tinker session):
Is it an expected behavior? Thank you, in advance!
Best and kind regards
Beta Was this translation helpful? Give feedback.
All reactions