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

Beacon's representation of Phoenix's Slots.

ComponentSlots don't exist on their own, but always belong to a Beacon.Content.Component.

Do not create or edit component slots 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.ComponentSlot{
  __meta__: term(),
  attrs: term(),
  component: term(),
  component_id: term(),
  id: term(),
  inserted_at: term(),
  name: term(),
  opts: term(),
  updated_at: term()
}