How do you write Ecto schema typespecs with nullable fields?

[Gigitsu]

@zorn

In some of my recent projects, I’ve preferred to model the schema type to be a description of a repo-sourced value, thus allowing me to type things like inserted_at: DateTime.t() instead of inserted_at: DateTime.t() | nil.

To allow for some functions which expected a non-repo-sourced value I would make a @type struct_t() :: %__MODULE__{}.

I like this approach, and your struct_t resembles my idea of a schema_t type, though with less enforcement. Thank you.

@dogweather

TypedEctoSchema and TypedStruct are life-savers. They eliminate unnecessary verbosity and make schema definitions readable.

I agree. I once wrote a typed_schema macro myself, but it started to feel like it was adding unnecessary complexity and non-standard conventions on top of Ecto, so I went back to manually crafted typespecs.