There was duplicate code for loading app based on this.configModelId
rename memoryStorage to storage
I'm guessing at one point it was named that because it was hardcoded to MemoryStorage. We allow providing any storage provider and it might not be memory. Example of FileStorage, RedisStorage, etc.
rename CLMemory to CLStorage
Better implies wrapper around BB.Storage.
Still need to find plan to remove SetAppAsync as that is higher level concept.
rename BotMemory to EntityState
Better implies the difference from BotState. Instead of comparing BotState to BotMemory which implies the difference is with Memory vs State it's now EntityState vs BotState which implies difference is the storage of entities vs bot state.
Normalize the three types of state
BotState, EntityState, MessageState
Rename conversationId to activityId
The InputQueue variables were named conversationId even though it wasn't, this was extremely misleading given that there are actual conversation ids.
remove redundant logic in GetRunningApp
There was duplicate code for loading app based on
this.configModelId
rename memoryStorage to storage
I'm guessing at one point it was named that because it was hardcoded to MemoryStorage. We allow providing any storage provider and it might not be memory. Example of FileStorage, RedisStorage, etc.
rename CLMemory to CLStorage
Better implies wrapper around BB.Storage. Still need to find plan to remove
SetAppAsync
as that is higher level concept.rename BotMemory to EntityState
Better implies the difference from BotState. Instead of comparing BotState to BotMemory which implies the difference is with Memory vs State it's now EntityState vs BotState which implies difference is the storage of entities vs bot state.
Normalize the three types of state
BotState, EntityState, MessageState
Rename
conversationId
toactivityId
The InputQueue variables were named conversationId even though it wasn't, this was extremely misleading given that there are actual conversation ids.