You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR: with the changes in the nightly build - optional/nillable settings in habitat are now forbidden
Just my two cents... most errors I've been seeing come directly from Habitat.
It seems that for whatever reason, when you check for raise_if_missing_settings, in the nightly build the check is way more stringent now. E.g:
Before, it was letting it pass if the setting was optional and you didn't provide it (aka: assuming it was there and nil)
Now, it fails. Aka: you have to always provide it - and setting it to null does not work (I didn't understand why though, but I didn't have the time to investigate it further)
What to do with that? Dunno :/ I doubt that even providing a default value would help in that case...
Yeah, I figured something might be up with that. I was trying to test a patch in Crystal and couldn't even get that to run because I was getting weird errors.
I'll see if I can dig in more to find out. Will probably need to do a git bisect since v1.12.1 to see what changed.
This just recently popped up in the last few days.
Maybe related? luckyframework/lucky#1872
The text was updated successfully, but these errors were encountered: