This repository was archived by the owner on Aug 19, 2025. It is now read-only.
✨ Add RedisPydanticStream backend #150
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Provides a new backend--
RedisPydanticStreamBackend--derived fromRedisStreamBackend. Instead of amessage: strbeing passed topublish, it takes a PydanticBaseModel. On the other side, it deserializes the object back into a Pydantic model. Now that I'm reviewing this, I think it'd be beneficial to add the following topublish:async def publish(self: typing.Self, channel: str, message: BaseModel) -> None: """Publish a message to a channel.""" msg_type: str = message.__class__.__name__ + + if msg_type not in self._module_cache: + self._module_cache[msg_type] = message.__class__ + message_json: str = message.model_dump_json() await self._producer.xadd(channel, {"msg_type": msg_type, "message": message_json})But it would only be useful in rare cases (dynamically created models or models at lower-than-module scope) or specifically in the test case, dropping the import and class declaration into the test itself.