-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.x] Retrieves applications from provider in Pulse connections recorder #194
Conversation
@colq2 I think this makes sense so would be happy to accept a PR here, but looks like tests are failing at the moment. Also, just wanted to confirm adding the options array should be addressed regardless of this PR? You just happen to be resolving that issue at the same time? |
Tests fail here. Make sure to fix them before marking as ready. |
@joedixon thanks, I will address the failing tests and update the PR. The options array is mandatory for this to work. Without the options property there is no way to get the options for the pusher client. Definitely not trying to squeeze two different things into same pr. |
Gotcha! I actually didn't mean to suggest you were squeezing two for one. It just seemed to me from reading your PR that the options array is missing from the current "config only" implementation. |
@joedixon no worries, I have to work on my description next time 🤓 Fixing the failing tests was pretty simple, just didn't have the time to resolve it earlier. |
Really nice addition, thank you! |
This PR updates how the connections recorder for Pulse retrieves applications. It now retrieves them from the registered ApplicationProvider. This extends the Application constructor with the options array.
Currently, the connections recorder does not work with providers other than the config provider. Another potential provider could be a database provider.
Let me know if you are willing to accept this kind of PR. I am happy to add test cases for this or update the PR.