You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR makes the ls method on the adapters compatible to the interface. However instead of removing a streaming ls, a new method was added to provide this feature. That means the equivalent named methods on Node\Directory now simply delegate to the adapter methods.
@clue Would it make sense to make ObjectStreamSink return an array instead of a SplObjectStorage? I've remembered after going through the code again (after all I've put the tests together with glue after a rather rough day), that it resolves with an object and not an array, which would be quite unexpected by the library user. Or would it make more sense to only adapt the specific ls methods? I will add a new commit for this to distinguish that.
@clue Would it make sense to make ObjectStreamSink return an array instead of a SplObjectStorage?
I'm not an expert for this particular repository, but I agree that an array is what I would have expected from this method. It's my understanding that this might make sense, but I would consider this to be out of scope of this PR also also perhaps @WyriHaximus can share some info here as well? 👍
@clue Would it make sense to make ObjectStreamSink return an array instead of a SplObjectStorage?
I'm not an expert for this particular repository, but I agree that an array is what I would have expected from this method. It's my understanding that this might make sense, but I would consider this to be out of scope of this PR also also perhaps @WyriHaximus can share some info here as well? 👍
Doing array for ObjectStreamSink would make perfect sense. Later on I want to change lsStream to return an RXPHPObservable anyway to make it more seamless and powerful for power users anyway tbh.
Later on I want to change lsStream to return an RXPHPObservable anyway to make it more seamless and powerful for power users anyway tbh.
While I can see some use for this, I'd like to discuss this more in depth before deciding on whether this makes sense. I agree a separate ticket or PR is the way to go 👍
Later on I want to change lsStream to return an RXPHPObservable anyway to make it more seamless and powerful for power users anyway tbh.
While I can see some use for this, I'd like to discuss this more in depth before deciding on whether this makes sense. I agree a separate ticket or PR is the way to go 👍
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
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 makes the
lsmethod on the adapters compatible to the interface. However instead of removing a streamingls, a new method was added to provide this feature. That means the equivalent named methods onNode\Directorynow simply delegate to the adapter methods.Unit tests have been adapted proportionally.