Artur Plysiuk

It just happens that such binaries are valid UUID as well. We simply try to guess the Ecto type by Elixir type, as we don't have other metadata in telemetry....

Hi @btkostner Having a public `Ecto.ERD.render` is a good idea. Just want to warn you that such usage adds compile-time dependencies with the schema modules. I'd suggest generating diagrams separately...

Now, I'm not sure about exposing a public function for rendering a document in order not to encourage usage in moduledocs. I need other scenarios why public function is needed...

It is already possible to render only some modules by using `map_node` parameter. The callback function must return `nil` for modules which must be removed. Multiple renders can be achieved...

In current implementation, customization of font is a requirement, as monospaced font is required for proper rendering of tables in nodes. It would be great if you point to things...

I tried this plugin, it is very interesting. However, selected/unselected states are solely plugin terms. We can add configuration for "unselected" states, but it doesn't mean that this improves readability,...

I found this crate https://crates.io/crates/getch it is quite small, we can play with it and Rustler and if it works okay, then implement as a separate package

There is an article mentioned in here https://github.com/ueberauth/ueberauth/issues/149#issuecomment-1015838222, and it uses local state, instead of encoding data to `state` param. `state`, in this case, is used just as a key....

``` [1] pry(main)> Qwerty.trace.wtf? (0.3ms) BEGIN Woohoo (0.3ms) COMMIT |-- # |-- Wrap/76 | |-- # | |-- a | `-- # `-- # => nil ``` It works! :tada:

@apotonick what is `|-- Wrap/76`? Why 76?