ekosz
Hi there, I have the following Reactor code:
defmodule CreateNewAccount do
use Reactor, extensions: [Ash.Reactor]
alias Accounts.Account
ash do
default_domain Accounts
end
input(:email)
input(:email_is_verified?)
create :account, Account do
inputs %{
email: input(:email),
email_is_verified?: input(:email_is_verified?)
} do
transform(fn input ->
input
|> Map.drop([:email_is_verified?])
|> Map.put(
:email_verified_at,
if input[:email_is_verified] do
nil
else
DateTime.now()
end
)
end)
end
end
end
But I’m getting the following error
Compiling 2 files (.ex)
== Compilation error in file lib/create_new_account.ex ==
** (Spark.Error.DslError) [CreateNewAccount]
reactor -> create -> account:
The create step `:account refers to an input named `email_is_verified?` which doesn't exist.
Did you mean `updated_at`, `created_at`, `id`, `email` or `email_verified_at`?
Looks like the DSL isn’t recognizing that I’m transforming the input. Is this a bug or am I just doing something incorrect?
Thank you!
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 5 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ekosz
Sounds good! Created the issue here: Issue · GitHub
Let me know if you would like me to add any additional context
jimsynz
Yeah that makes sense. We can’t validate the keys statically if the input is being transformed. @ekosz do you mind opening an issue on ash (it’s an
Ash.Reactorbug) and I’ll tackle it once I am back from my holiday. In the mean time you can move that behaviour into a change on the underlying action or process it as a seperate step so that the input map has the correct keys.zachdaniel
Ah, right. @jimsynz i think with the transform option we’d have to disable the check for the input map keys wouldn’t we?
ekosz
Hi @zachdaniel ! I get that, but aren’t I transforming the input using the
transformoption to remove the:email_is_verified?option and add a:email_verified_at(which it does accept)?Or is that not what the transform option does?
zachdaniel
Took me a while to notice this
The error message is confusing here due to the overloaded term “input”. What reactor is doing here is telling you that the create action on
Accountthat it is calling does not accept an input calledemail_is_verified?.So you’d need either an argument on that action or to accept that field as input using
acceptto resolve this error.