<FromGitter>
<Blacksmoke16> @drujensen looks like none of our spec models declare a nilable type, so CI didn't catch it.
<FromGitter>
<Blacksmoke16> How do we want to handle it, could either raise a compile time exception so people *cant* do it, otherwise the type of the property would be like `Union(Int32 | Nil | Nil)`, dunno if that would cause any issues later on
<FromGitter>
<Blacksmoke16> or just strip Nil out when doing the casting
feepbot has quit [Ping timeout: 244 seconds]
feepbot has joined #amber
<FromGitter>
<nsuchy> @elorest yeah I just don't want the folder and its files to exist
<FromGitter>
<nsuchy> would be a nice feature to have
<FromGitter>
<nsuchy> an option in amber.yml to disable specs
<FromGitter>
<Blacksmoke16> if anything it would be an optional arg id imagine
<FromGitter>
<Blacksmoke16> `amber g controler blog --no-spec`
<FromGitter>
<Blacksmoke16> `in spec/spec_models.cr:8: The type of Teacher#age cannot be a Union. Use the 'field!' macro to declare a not nilable field.` that'll work
<FromGitter>
<Blacksmoke16> `The type of Teacher#age cannot be a Union. The 'field'` macro declares they type as nilable by default. Use the 'field!' macro to declare a not nilable field.`
vivus has joined #amber
vivus has quit [Read error: Connection reset by peer]