fix(drivers-event-listener-griptape-cloud): add type/timestamp fallbacks for custom events #1758
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.
Describe your changes
Problem:
Users can publish custom events by passing a dict to
publish_event
:griptape/griptape/drivers/event_listener/base_event_listener_driver.py
Lines 30 to 31 in d15b2a6
GriptapeCloudEventListenerDriver
makes assumptions about what these events will contain:griptape/griptape/drivers/event_listener/griptape_cloud_event_listener_driver.py
Lines 72 to 77 in 7af49da
Solution:
Add fallbacks for these keys:
griptape/griptape/drivers/event_listener/griptape_cloud_event_listener_driver.py
Lines 73 to 78 in d15b2a6
Issue ticket number and link
NA