What is the best way to define Elixir App wide constants and errors?.In languages like go lang we export and import constants and errors. What is the idiomatic or best, the De facto industry standard of Elixir community or generally design pattern for it? requirements: we should be able to match…

I’m also interested in hearing answers to this, especially for options that don’t spread compile time dependencies far and wide.

I had replied to your old post and I’m reposting my reply but with a few additions. For many projects, I’ve often needed to use constants/enums. So I made a lib for it: SimpleEnum . I’ll let you read the thread for more details, but to sum up: Enums can be used in guards There are no dependencies…

Thank you @ImNotAVirus , I would like to explore macros.

To be fair I’d just do this: defmodule MyApp.UnixErrors do defmacro __using__(_opts) do quote do @bad_argument :badarg @invalid :einval end end end defmodule MyApp.UserModule1 do use MyApp.UnixErrors def hello(), do: @bad_argument end This too is some level of compile…

able to match them in guards and clauses?

yes. I have to assign to temporary variables.And also cant have capital letters defmodule Nat.Constants do @moduledoc false defmacro __using__(_) do quote do @st1 "urn:schemas-upnp-org:device:InternetGatewayDevice:1" @igd_device_upnp1 "urn:schemas-upnp-org:device:InternetGatewa…

[image] apoorv-2204: And also cant have capital letters Why not? For example these: [image] apoorv-2204: @supported_protocols [Upnpv1, Upnpv2, PMP] …are basically atoms.

[image] Also cant use them in the match and clauses.

Ah, you mean the module attributes can’t start with a capital letter. Can’t help you there, but I don’t see why would that be a hard requirement for you either.

Shared Common Constants/Errors Across the Application

Questions & Help Questions

apoorv-2204 September 13, 2023, 1:39pm 10

Also cant use them in the match and clauses.