ilya-kolpakov
By defining a struct one guarantees that the instances’ keys are exactly those provided in the definition. By including a key within the enforce_keys attribute one ensures that the corresponding values cannot be nil.
In my view, the attribute name enforce_keys suggests that the keys listed there will be always present in the struct (which is actually the case for all keys provided in the definition) rather than that the corresponding values cannot be nil.
Trending in Discussions
As the title says, please share what you’ve been up to with Elixir. Whether that’s been learning it, looking into it, making stuff with i...
New
I want to open this thread for you all to discuss and help those who really like Ash but are still hesitant to use it in a real project. ...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
I’m posting this in response to Jose’s recent tweet (Cr. link) :
People are sleeping on Elixir for a coding harness:
Hot-code swappi...
New
Hello,
I wrote Stop My Hand, a Scattergories-like web application using Phoenix/LiveView as my learning project for Elixir (after readin...
New
It would be helpful to have a list of companies worldwide that hire engineers without prior experience in Elixir. Often, it can be quite ...
New
Anyone running long-lived stateful processes on BEAM? We’re building an AI agent runtime and would love to compare notes.
We’re a small ...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
chrismccord
This is indeed the case of how
enforce_keysbehaves. Where are you seeing otherwise? Perhaps the docs could be clearer but the current behavior is exactly as describedilya-kolpakov
In my view, the keys are always in the struct as long as they are listed in definition:
In my view, one could say that “all the keys listed in the definition are enforced to be present in the struct instance”. And by looking at code itself one could expect that “enforce_keys” does exactly that (meaning the presence of keys not listed under “enforce_keys” within the struct is optional).
What
enforce_keysdoes is that it makes sure the corresponding values cannot benil. Hence these are not the keys that are “enforced” byenforce_keys. It is rather the non-nilness of values that is enforced. Hence the nameenforce_keysis somewhat misleading and non-transparent (IMO).Docs are fine. IMO, guess clear docs are not a substitute for clear unambiguous names (as they obviate the need to look in the docs in the first place).
EDIT: hopefully better explanations
chrismccord
Sorry, I was saying that your ideal view is the current behavior. For example:
Enforce keys doesn’t care about nil values, only keys. Does that clear things up?
ilya-kolpakov
Oh I see. So keys listed under
enforce_keysmust be present in the constructor and that’s all. They are, in a sense, like positional args to functions as they need to be always present.