Marcin Dziewulski

@erlandsona 👋 it looks doable, I will handle this over the weekend :) or you can create a pull request with implementation and I'll be happy to merge it in,...

hello @nikgraf! 👋 thanks for posting this issue, could you try with [v2.1.0](https://github.com/mobily/stacks/releases/tag/v2.1.0), please? also, if this still occurs, a repro repo would be helpful! 🙏

hey @jsamr, I'm looking into it, however, I think with the current implementation (that isn't based on `cloneElement`) and how `react` works, it isn't trivial. I'm aware that it's a...

@jsec @WidgetKing @alexn-s hey there! 👋 this is definitely on my roadmap, sneak peek: I'm currently working on three following modules: - Async (equivalent to `fp-ts` Task) - AsyncResult (TaskEither)...

@jrolfs `D.merge` uses `Object.assign` under the hood :)

@eckertalex sounds like a great idea, do you have any suggestion on how to tackle TS signature of `D.unsafeSelectKeys`?

hey @anthony-khong 👋 thanks for your questions! 1. that sounds like proper solutions for both, but first I need to look into it 2. actually, you're right! it definitely should...

ad 2. it's been fixed and published in `v3.1.1` 🚀

> if we already have D.prop, it may make sense to have D.propIn instead of D.getIn that’s actually a good point in terms of the naming convention, I took the...

👋 hey again @anthony-khong! > I'm curious to know what you actually do during development! I did some changes to improve this process, so basically, for development purposes, you can...