dokicro

dokicro

Hi,

I am new to elixir and here is part of the code I dont like

slider =  case Map.has_key?(attrs, :slider_id) do
  true -> get_slider!(attrs.slider_id)
  false -> get_slider!(attrs["slider_id"])
end

Reason for this is because when I do attrs = Map.put(attrs, :slider_id, slider.id) in sliders_test map key is atom

But when I do the same thing in slider_controller_test map key is string.

Showing Posts 1 to 10

kokolegorille

kokolegorille

You could…

slider = Map.get(attrs, :slider_id) || Map.get(attrs, "slider_id")

As a rule of thumb, expect data coming from outside to be “key”, and after cast to be :key.

sorentwo

sorentwo

Oban Core Team

You would be best served treating all incoming params as having string keys. If you must accept either atom or string keys, then using Map.get(“key”) || Map.get(:key) would be clearer than a case.

dokicro

dokicro OP

Thanks guys for your help, I agree that this is much cleaner syntax.

Nicd

Nicd

To elaborate a bit, the reason why map keys from external sources (like user input) are strings, is that atoms are not garbage collected and there is a set maximum amount of atoms available in the system. If you exceed that amount, the VM will crash. So that’s why you shouldn’t create atoms from user input for example.

dokicro

dokicro OP

But why is phx gen generating tests maps with keys?
I tried to put slider_id as string but I got this:
expected params to be a map with atoms or string keys, got a map with mixed keys

So I should convert all pregenerated keys from atoms to string?

Example:
@valid_attrs %{description: "some description"}
to
@valid_attrs %{"description" "some description"}

mbuhot

mbuhot

The test maps should be automatically serialised to json by the phoenix test helpers, then deserialised to string-keyed maps in the Plug.Parsers plug declared in your endpoint module.

dokicro

dokicro OP

They are only in controllers tests…

LostKobrakai

LostKobrakai

Params in contollers have string keys because anybody can send you any param and creating an atom for those would be a attack vector to crash the vm. It’s still generally adviced to work with atom keys in your business part of the app and to sanitize and atomize params before passing things forward into it.

sharkvan

sharkvan

This is interesting. In test that are generated by phx.gen.html the controller tests will have a fixture function that creates a test record with Ecto. But there is no changing of the atom keys to string keys. So if you do anything inside the context modules where you expect a string key from the controller your tests fail but the website works. Hmm, not great.

mbuhot

mbuhot

If you are getting anything other than string keyed params in Controllers then there is something wrong with the test.

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
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
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews