Alex Okrushko
Alex Okrushko
Thank you so much @ngfelixl for getting this going! 🙏 I'll peeked into the suggested tests and would provide some feedback a bit later.
@peterhe2000 let's take that discussion to https://discord.gg/ngrx :)
Even through there is an expectation that `next` callback doesn't throw an error, we can adjust to catch errors in the `next` as well, I don't think there's a problem....
Generally, I like the idea. @timdeschryver @markostanimirovic maybe we can explore it past v11?
This article from @cartant can be also linked there: https://ncjamieson.com/avoiding-switchmap-related-bugs/
`createSelectorFactory` is a way to extend or adjust the behavior of selectors. Instead of increasing the API surface of selectors I'd suggest to use this function instead. e.g. for measuring...
I don't think we can do anything about it - it's a broken upstream dependency.
Hey all, So the closure strips properties from effects, because "they are not used". To force them to be there you can declare the interface. That's the best workaround for...
Hi @rainerhahnekamp. There's definitely a need for encapsulation, so that some props/methods can remain private. There are a number of approaches that can do that: 1. Your current proposal, doing...
Looks like @JordanShurmer fixed it in https://github.com/JordanShurmer/eleventy-plugin-toc and released the plugin under `eleventy-plugin-nesting-toc`. Maybe let's merge the fixes and keep one ToC plugin? Thank you