Bernardo Amorim

I'll try to see if I can figure out a way myself, but probably will only have time for that early November as well, but will give another shot at...

I gave it a shot today, but there is still a long way to go I guess. Here is the WIP commit: https://github.com/IvanRublev/Domo/commit/231f072454187c48d85cdb9df9f819a554fc6948 What is missing is mainly is how...

I'd like to know if there is still interest. I started to play around with the idea. As you can see [here](https://github.com/bamorim/typed_ecto/blob/master/test/typed_ecto_schema_test.exs). I think integrating with Ecto is a whole...

@ejpcmac after going through integrating with Ecto (I'm almost finished). I don't think it is possible to create a one-size-fits-all solution. The reason is that this lib defines it's own...

Also, since `Ecto.Schema` but doesn't only use field for defining fields, instead of defining my own fields, I made a "syntax sugar" that transforms all `field(:my_field, :string)` into: ```elixir field(:my_field,...

Just FYI, I released the lib: https://github.com/bamorim/typed_ecto_schema

@parroty For some reason it is failing on github actions. Do you know what is happening?

Hi, I'm tackling this issue right now but I'd like to discuss about the sorting thing. When generating the new CODEOWNERS file after sorting, should we keep the comments? Comments...

Also, how should we handle patterns with multiple owners? The only reasonably solution is to treat a collection of owners as a "unique owner" when grouping Something like ``` #...

Another question: should we check for consistency on this command as well? Or just rewrite the file?