summaryrefslogtreecommitdiff
path: root/lib/elixir/pages
diff options
context:
space:
mode:
authorJohn Mertens <mertonium@users.noreply.github.com>2018-04-19 23:20:50 -0700
committerAleksei Magusev <lexmag@me.com>2018-04-20 08:20:50 +0200
commit384751fd8ec1c4fba7a6f8b766b8bf209620156e (patch)
tree1a73de48df61617251e5a56a8d29f1c1d2aa14cc /lib/elixir/pages
parent74e666156906974082f6b4d34dfbe6988d6465c0 (diff)
downloadelixir-384751fd8ec1c4fba7a6f8b766b8bf209620156e.tar.gz
Fix typo (#7570)
Diffstat (limited to 'lib/elixir/pages')
-rw-r--r--lib/elixir/pages/Library Guidelines.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/elixir/pages/Library Guidelines.md b/lib/elixir/pages/Library Guidelines.md
index 7ded5c2ca..ca3d9999c 100644
--- a/lib/elixir/pages/Library Guidelines.md
+++ b/lib/elixir/pages/Library Guidelines.md
@@ -96,7 +96,7 @@ def my_fun(some_arg, file_to_write_to, options \\ []) when is_binary(file_to_wri
Elixir also leverages pattern matching and guards in function clauses to provide clear error messages in case invalid arguments are given.
-This advice does not only apply to libraries but to any Elixir code. Every time you receive multiple options or work with external data, you should validate the data at the boundary and convert it to structured data. For example, if you provide a `GenServer` that can be started with multiple options, you want to validate those options when the server starts and rely only on structured data throughout the process life cycle. Similarly, if a database or a socket gives you a map of strings, after you receive the data, you should validate it and potentially convert it to a struct of a map of atoms.
+This advice does not only apply to libraries but to any Elixir code. Every time you receive multiple options or work with external data, you should validate the data at the boundary and convert it to structured data. For example, if you provide a `GenServer` that can be started with multiple options, you want to validate those options when the server starts and rely only on structured data throughout the process life cycle. Similarly, if a database or a socket gives you a map of strings, after you receive the data, you should validate it and potentially convert it to a struct or a map of atoms.
### Avoid application configuration