Change in how `Ash.Changeset.force_change_attributes` handles `nil` values?
i'm currently in the process of upgrading to the latest version. there seems to have been a change in how
at least, that what i seem to be observing.
here's a simple example:
why is that important for me?
we implement our own data layer for hubspot resources and i have one use case where i want to forcefully overwrite data and even set attributes to nil if that should be the case.
in the data layer implementation i'm currently relying on attributes to detect what attributes i need to update on hubspot. see screenshot 3, the
Ash.Changeset.force_change_attributesat least, that what i seem to be observing.
here's a simple example:
%JdlEngine.Hubspot.Contact{} |> Ash.Changeset.for_update(:update, %{}) |> Ash.Changeset.force_change_attributes(%{ city: "vice city", })attributes: %{city: "vice city"}%JdlEngine.Hubspot.Contact{} |> Ash.Changeset.for_update(:update, %{}) |> Ash.Changeset.force_change_attributes(%{ city: nil, })attributes: %{}why is that important for me?
we implement our own data layer for hubspot resources and i have one use case where i want to forcefully overwrite data and even set attributes to nil if that should be the case.
in the data layer implementation i'm currently relying on attributes to detect what attributes i need to update on hubspot. see screenshot 3, the
cast_changesetcity: nil
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Was this page helpful?
