Foundry. Chat. Session
(foundry v0.1.1)
Copy Markdown
Chat session resource backed by Mnesia disc_copies.
Each session has a unique ID, a list of messages (role + content), and timestamps. Mnesia ensures persistence across restarts without requiring a separate database.
Mnesia Setup
The Mnesia table is created and initialized at application startup in
Foundry.Application.init_mnesia/0. The table name is :foundry_chat_sessions.
Summary
Types
@type t() :: %Foundry.Chat.Session{ __lateral_join_source__: term(), __meta__: term(), __metadata__: term(), __order__: term(), aggregates: term(), calculations: term(), created_at: term(), id: term(), message_count: term(), messages: term(), model: term(), session_digest: term(), session_id: term(), title: term(), updated_at: term() }
Functions
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)})
|> Ash.create()
Same as input/1, except restricts the keys to values accepted by the action provided.