# `PhoenixKitKnowledgeBase.Schemas.Folder`
[🔗](https://github.com/BeamLabEU/phoenix_kit_knowledge_base/blob/v0.1.0/lib/phoenix_kit_knowledge_base/schemas/folder.ex#L1)

An index row for a directory inside a vault.

There is no `parent_uuid`. The filesystem already expresses the hierarchy, and
a second representation in the database is a second thing that can disagree
with the disk — so the tree is rebuilt from `relative_path` when the sidebar
needs it (`PhoenixKitKnowledgeBase.Notes.folder_tree/1`).

Folders play no part in `[[wiki-link]]` resolution, which matches on title
across the vault and only consults paths to break a tie.

# `t`

```elixir
@type t() :: %PhoenixKitKnowledgeBase.Schemas.Folder{
  __meta__: term(),
  inserted_at: term(),
  name: term(),
  relative_path: term(),
  updated_at: term(),
  uuid: term(),
  vault: term(),
  vault_uuid: term()
}
```

# `changeset`

Changeset for an indexed directory.

`:name` is derived from the path rather than accepted separately — they can
only ever disagree by mistake.

---

*Consult [api-reference.md](api-reference.md) for complete listing*
