Packages
telegex
1.2.1
1.9.0-rc.0
1.8.0
1.7.0
1.6.0
1.5.0
1.4.2
1.4.1
1.4.0
1.3.2
1.3.1
1.3.0
1.2.3-dev
1.2.2
1.2.1
1.2.0
1.1.1
1.1.0
1.0.1
1.0.0
1.0.0-rc.10
1.0.0-rc.9
1.0.0-rc.8
1.0.0-rc.7
1.0.0-rc.6
1.0.0-rc.5
1.0.0-rc.4
1.0.0-rc.3
1.0.0-rc.2
1.0.0-rc.1
1.0.0-rc.0
0.1.10
0.1.9
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.1.0-rc.11
0.1.0-rc.10
0.1.0-rc.9
0.1.0-rc.8
0.1.0-rc.7
0.1.0-rc.6
0.1.0-rc.5
0.1.0-rc.4
0.1.0-rc.3
0.1.0-rc.2
0.1.0-rc.1
0.0.4
0.0.3
0.0.2
0.0.1
A Telegram bot framework, with its client-side based on data and code generation, boasts unparalleled adaptation speed and correctness for new versions.
Current section
Files
Jump to
Current section
Files
priv/type_template.ex.eex
defmodule Telegex.Type do
@moduledoc "All types used in the Bot API responses."
use Telegex.TypeDefiner
@type error :: Telegex.Error.t() | Telegex.RequestError.t()
<%= for union_type <- @union_types do %>
defunion(<%= union_type.name %>, "<%= union_type.description %>", <%= union_type.types %>, <%= union_type.discriminant %>)
<% end %>
<%= for args <- @type_args do %>
deftype(<%= args.name %>, "<%= args.description %>", <%= args.fields %>)
<% end %>end