docs: Makes the phrasing more smooth and reasoning more clear (#28020)

Updated the phrasing and reasoning on the "abstraction not receiving
much development" part of the documentation

---------

Co-authored-by: ccurme <chester.curme@gmail.com>
This commit is contained in:
Zapiron 2024-11-12 01:17:29 +08:00 committed by GitHub
parent f695b96484
commit 0b85f9035b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -108,9 +108,8 @@ And specific backend implementations of abstractions:
| `SQLiteEntityStore` | A specific implementation of `BaseEntityStore` that uses SQLite as the backend. |
| `UpstashRedisEntityStore` | A specific implementation of `BaseEntityStore` that uses Upstash as the backend. |
These abstractions have not received much development since their initial release. The reason
is that for these abstractions to be useful they typically require a lot of specialization for a particular application, so these
abstractions are not as widely used as the conversation history management abstractions.
These abstractions have received limited development since their initial release. This is because they generally require significant customization for a specific application to be effective, making
them less widely used than the conversation history management abstractions.
For this reason, there are no migration guides for these abstractions. If you're struggling to migrate an application
that relies on these abstractions, please: