Draft
Conversation
1 task
gehrisandro
force-pushed
the
add-events
branch
from
fc0e5b6 to
049aa14
Compare
# Conflicts: # src/Resources/ThreadsMessages.php
|
Besides the Laravel Pulse use-case, we got some people asking to instrument this library in our Sentry Laravel SDK. Is there any appetite to move forward with this PR? |
|
I am interested in this - to centrally log requests/responses and track costs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds the ability register an event dispatcher.
When a request has been handled successfully and an event dispatcher is registered, a
RequestHandledevent will be dispatched.The event contains the initial
Payloadof the request and theResponse.This feature is required to create a
Recorderfor Laravel Pulse in the openai/laravel repository.Todos:
Transportablecontract