Well, I've been talking about stepping forward to take over as PSR-14 Editor
for a few weeks now. I should probably go ahead and do it since there seems
to be interest.
Before we start showing code, I'd prefer to step back and define the specific
use cases we want to target. Benni's list belo
Is this the right forum for putting forward examples of our own work as
potential candidates? I’ve been working on one under the name event interop
(much as PSR-11 was born from) but it seems we all have similar ideas.
Shall we start showing some code examples?
--
Barney Hanlon
On 13 March 2018
Hey folks,
I've been meaning to share my feedback for quite some time on that.
We've looked into different implementations a lot and we (TYPO3 dev) would only
consider Event Manager if we're talking about immutable events. And event is
triggered, could have parameters, but the event itself shou
Am 13.03.2018 um 10:58 schrieb Barney Hanlon:
> I would recommend that setParam or indeed any setting of properties be out
> of the spec. In my opinion, Events and Commands should both be immutable,
> but people are open to implement configuration post-construction if they
> wish. But if the spec
Uri uri = new Uri("...");
try
{
HttpClient client = new HttpClient();
var downloadTask = client.GetAsync(uri);
downloadTask.Progress = (result, progress) =>
{
Debug.WriteLine("===start===
I would recommend that setParam or indeed any setting of properties be out
of the spec. In my opinion, Events and Commands should both be immutable,
but people are open to implement configuration post-construction if they
wish. But if the spec defines these, then the spec is defining the payload
of
IMHO, looks like we are nowhere with the event manager standard. There are
a handful of implementations, most very recent. Not aware of any consumers,
besides my code.
I believe there are many things wrong with that standard. Right now, I'm
working on a proposal of how it can be changed. Meanwh
