Demo.Accounts.Profile (ash_admin v0.2.19) View Source
no description
Link to this section Summary
Functions
Callback implementation for Ash.Type.apply_constraints_array/2
.
Callback implementation for Ash.Type.cast_input/2
.
Callback implementation for Ash.Type.cast_stored/2
.
Callback implementation for Ash.Type.dump_to_native/2
.
Callback implementation for Ash.Type.handle_change_array/3
.
Validates that the keys in the provided input are valid for at least one action on the resource.
Callback implementation for Ash.Type.prepare_change_array/3
.
Callback implementation for Ash.Type.storage_type/0
.
Link to this section Types
Specs
t() :: Demo.Accounts.Profile
Link to this section Functions
Callback implementation for Ash.Type.apply_constraints_array/2
.
Callback implementation for Ash.Type.cast_input/2
.
Callback implementation for Ash.Type.cast_stored/2
.
Callback implementation for Ash.Type.dump_to_native/2
.
Callback implementation for Ash.Type.handle_change_array/3
.
Validates that the keys in the provided input are valid for at least one action on the resource.
Raises a KeyError error at compile time if not. This exists because generally a struct should only ever
be created by Ash as a result of a successful action. You should not be creating records manually in code,
e.g %MyResource{value: 1, value: 2}
. Generally that is fine, but often with embedded resources it is nice
to be able to validate the keys that are being provided, e.g
Resource
|> Ash.Changeset.for_create(:create, %{embedded: EmbeddedResource.input(foo: 1, bar: 2)})
|> MyApp.Api.create()
prepare_change_array(old_values, new_uncasted_values, constraints)
View SourceCallback implementation for Ash.Type.prepare_change_array/3
.
Callback implementation for Ash.Type.storage_type/0
.