Arne Bertrand
Arne Bertrand
apologies for the long delay of the response, I've been swamped with deadlines and other concerns so the logging experiment has fallen down the backlog. I haven't completely thought this...
Yeah I find that with a good diary name the message can become a bit redundant. It's also a slight deviation from the original `console` api which might trip up...
I see what you mean, but I'd disagree. Simple usecase for example is logging method calls. I use a decorator to make this easy to add to interesting methods. It...
yeah I totally missed that trick to just make a custom createLogger :D I think that basically covers my entire usecase now that I think about it, the inherited diary...
We're seeing similar problems in our project, were the 2 prs closed soon before you generated the changelog by any chance? We're suspecting that timing has something to do with...
note we (almost) never cherry-pick and still see dropped prs, there may be multiple issues playing here
To be honest I don't really see the added value of the model creator section. The original article is eh, "sparse" at best, and doesn't really explain anything about mu-cl-resources....
Incidentally, if I can rely on tree-shaking (can I?), I could just static import and just not call the `applyDevTools` function. That still leaves this as a bug though
Interesting. It may be on github's end, I'll monitor and see if I can get a useful repro
I haven't encountered this any more, and you did answer the original question, so I think you can close this issue. Thank you for your time.