View Source Glific.AccessControl.TriggerRole (Glific v5.1.6)
A pipe for managing the role triggers
Link to this section Summary
Functions
Standard changeset pattern we use for all data types
Filtering entity object based on user role
Creates a access control.
Delete trigger roles
Update trigger roles based on add_role_ids and delete_role_ids and return number_deleted as integer and roles added as access_controls
Link to this section Types
@type t() :: %Glific.AccessControl.TriggerRole{ __meta__: Ecto.Schema.Metadata.t(), id: non_neg_integer() | nil, organization: Glific.Partners.Organization.t() | Ecto.Association.NotLoaded.t() | nil, organization_id: non_neg_integer() | nil, role: Glific.AccessControl.Role.t() | Ecto.Association.NotLoaded.t() | nil, role_id: term(), trigger: Glific.Triggers.Trigger.t() | Ecto.Association.NotLoaded.t() | nil, trigger_id: term() }
Link to this section Functions
@spec changeset(t(), map()) :: Ecto.Changeset.t()
Standard changeset pattern we use for all data types
@spec check_access(Ecto.Query.t(), Glific.Users.User.t()) :: Ecto.Query.t()
Filtering entity object based on user role
@spec create_trigger_role(map()) :: {:ok, t()} | {:error, Ecto.Changeset.t()}
Creates a access control.
examples
Examples
iex> create_trigger_role(%{field: value})
{:ok, %TriggerRole{}}
iex> create_trigger_role(%{field: bad_value})
{:error, %Ecto.Changeset{}}
Delete trigger roles
Update trigger roles based on add_role_ids and delete_role_ids and return number_deleted as integer and roles added as access_controls