Aggregatable and consistent errors for Elixir
Find a file
2024-03-14 18:02:18 -04:00
.github init 2024-03-14 17:59:44 -04:00
config init 2024-03-14 17:59:44 -04:00
documentation/tutorials init 2024-03-14 17:59:44 -04:00
lib init 2024-03-14 17:59:44 -04:00
test init 2024-03-14 17:59:44 -04:00
.check.exs init 2024-03-14 17:59:44 -04:00
.credo.exs init 2024-03-14 17:59:44 -04:00
.doctor.exs init 2024-03-14 17:59:44 -04:00
.formatter.exs init 2024-03-14 17:59:44 -04:00
.gitignore init 2024-03-14 17:59:44 -04:00
.tool-versions init 2024-03-14 17:59:44 -04:00
CHANGELOG.md chore: release version v0.1.0 2024-03-14 18:02:18 -04:00
FUNDING.yml init 2024-03-14 17:59:44 -04:00
LICENSE init 2024-03-14 17:59:44 -04:00
mix.exs init 2024-03-14 17:59:44 -04:00
mix.lock init 2024-03-14 17:59:44 -04:00
README.md init 2024-03-14 17:59:44 -04:00

Splode

Splode helps you deal with errors and exceptions in your application that are aggregatable and consistent. The general pattern is that you use the Splode module as a top level aggregator of error classes, and whenever you return errors, you return one of your Splode.Error structs, or a string, or a keyword list. Then, if you want to group errors together, you can use your Splode module to do so. You can also use that module to turn any arbitrary value into a splode error.

See the documentation on hex for more information