persona

type Persona[D state.Initializable[D, *D], S state.Initializable[S, *S]] struct {
	// The Name of the Persona; this is used in messaging and to determine the name of the Persona's state file.
	// Every Persona must have a name - if one is not specified, it defaults to "default" when the Persona is
	// initialized; this is used for the name of the state file on disk as "{Name}.yaml".
	//
	// Example Behavior:
	//
	// With Name "foo":
	//     "foo.yaml"
	// With Name "foo_bar.baz":
	//     "foo_bar.baz.yaml"
	Name string
	// The Kind of Persona this is. The Name field is used in log messaging/displays about the Persona while the
	// FolderName field is used to determine where to save it and look for it when loading. If not specified, it
	// defaults to state.Kind{Name: "persona", FolderName: "personas"}
	//
	// Example Behavior:
	//
	// With root folder "myApp", Kind.FolderName "users", and Name "foo":
	//     "myApp/saves/foo.yaml"
	// With root folder "myApp", Kind.FolderName "modes", and Name "interactive":
	//     "myApp/modes/interactive.yaml"
	Kind state.Kind
	// The handler for this Persona's state to enable file discovery and save/load operations.
	Handle *state.Handle
	// Personas have Data of the type you specify when instantiating them. It must be a struct of the information related
	// to this Persona specifically. This can be any struct you want as long as:
	//
	// 1. It has an Initialize() method that returns a pointer to the data structure itself. You want to make sure that
	// this method sets sensible defaults for the data if you need any - otherwise it can just return a pointer to an
	// empty instance of the data type.
	//
	// 2. It can be marshalled/unmarshalled by viper. In general, you don't need to worry about this unless you're doing
	// something very complex. No such errors or issues have been reported, but viper is what is being used further down
	// the stack to load/save the state file for an instance so if viper can't handle it the instance will error.
	Data D
	// Settings is a struct that determins how this Persona should behave in the application. The Settings field is always
	// determined by the application developer and can be any struct so long as it has an Initialize() method which
	// returns a pointer to itself.
	// Personas have Settings of the type you specify when instantiating them and determine how this Persona should behave
	// in the application. The Settings can be any struct you want as long as:
	//
	// 1. It has an Initialize() method that returns a pointer to the settings struct itself. You want to make sure that
	// this method sets sensible defaults for the data if you need any - otherwise it can just return a pointer to an
	// empty instance of the data type.
	//
	// 2. It can be marshalled/unmarshalled by viper. In general, you don't need to worry about this unless you're doing
	// something very complex. No such errors or issues have been reported, but viper is what is being used further down
	// the stack to load/save the state file for an instance so if viper can't handle it the instance will error.
	Settings S
}