Elixir code evaluation in Playground attributes

[xxdavid]

Hi again, @cblavier! For a few weeks, I've been playing with the idea of allowing almost-arbitrary Elixir code to be used as an attribute value in the Playground. It's seems a pity to me that only a subset of attributes can be modified in the Playground, often times the attributes I would like to edit are locked.

What do you think about evaluating the value in case its type is not a string? For example, that it would be possible to pass [%{id: "john", name: "John"}, %{id: "jane", name: "Jane"}] to the rows attribute of the table/1 component from CoreComponents. Or passing %{name: "my-input", disabled: true} to the global rest attribute of an input.

It might be not safe to execute arbitrary code though, because in case the Storybook was running on a public server, this would give a random Storybook visitor full control over the server. Therefore, I suggest keeping this feature opt-in, disabled by default. Additionally, it might be useful to use dune or something like that.

[cblavier]

Custom code evaluation was indeed limited for security reasons.
I like the idea of using something like dune, I wasn't aware of this lib.

We could also consider implementing custom slot templates.
However, would it be too cumbersome to write them in a textarea?

Let's add it to the backlog! 📚

[xxdavid]

Great! For me, it'd be totally fine to use a plain textarea to edit the slots. :)