Replies: 2 comments 4 replies
-
You're fine. Thank you for thinking about this problem. So long as you're going to propose a well-thought out change, feel free to send a PR (maybe a draft PR if you're uncertain) so that at least I can readily see the diff that you're applying. As it is, I have to sort through the whole 'file' you've shared to find the differences. I think you already realized an issue with this proposed fix, because you adapted to it by calling We're in an unfortunate here. I suppose the case could be made that as a breaking change, I ought to bump the major version number. I could still do that -- revert the fix, ship a servicing release, then ship a new major version with the fix. I'm curious how hard this is impacting you. Is it that you can't change the calling code to adapt for some reason? Or is it that it's a pain to add handlers for all events? What if I added a |
Beta Was this translation helpful? Give feedback.
-
Done. I hope it 's right (It's my first PR) .
Indeed.
I'm assuming that WillRead, WillWrite, WillRead and DidRead were being used to being notified of this events independently of the specific api (signature) invoked. For new proyects, it´s obviously preferable to use the ad-hoc events (DidReadSpan, DidReadMemory or the new DidReadArraySegment, for example)
It's not hard impact for me. It was an unexpected behavioural change. I admit that usually I update dependencies without reading the Release notes. Unfortunatelly it's an extended practice.
Great!. I would like it. But it will be usefull for new projects. I hope my contribution is that and not only annoyance. Thank you for your patience and sorry for the inconveniences. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I didn't felt happy with Breaking change introduced in 2.11.79.
So I'm propossing a way to maintain compatibility with previous versions yet introducing the new Events.
I've added new Events (WillReadArraySegment, DidReadArraySegment, WillWriteArraySegment and DidWriteArraySegment to raise when methods signatures are specifically needed, and maintain the WillRead, DidRead, WillWrite and DidWrite events original behaviour.
I think this will remove the Breaking Change.
This is the suggested code:
It´s my first time so, I apologize if I am not respecting the etiquette.
Regards.
Beta Was this translation helpful? Give feedback.
All reactions