View Source Beacon.Content.ComponentSlotAttr (Beacon v0.3.3)

Beacon's representation of Phoenix's Slot attributes.

ComponentSlotAttrs don't exist on their own, but always belong to a Beacon.Content.ComponentSlot, which in turn belongs to a Beacon.Content.Component.

Do not create or edit component slot attrs manually

Use the public functions in Beacon.Content instead. The functions in that module guarantee that all dependencies are created correctly and all processes are updated. Manipulating data manually will most likely result in inconsistent behavior and crashes.

Summary

Types

t()

Types

t()

@type t() :: %Beacon.Content.ComponentSlotAttr{
  __meta__: term(),
  id: term(),
  inserted_at: term(),
  name: term(),
  opts: term(),
  slot: term(),
  slot_id: term(),
  struct_name: term(),
  type: term(),
  updated_at: term()
}