Currently we only have a simple "array" based ChatHistory implementation, it would be nice if we could have a default migration and model that represents this that can be persisted in whatever database the user is already using.
Planned, but will probably be implemented in a different way, completely change how history works and tailor it to the new direction (deeper laravel integration, more usecase specific functionality etc)
Currently we only have a simple "array" based ChatHistory implementation, it would be nice if we could have a default migration and model that represents this that can be persisted in whatever database the user is already using.