jeffijoe / libx Goto Github PK

As there wasn't any update in the past 1,5 years, what do you think about merging all open PRs related to dependency upgrades (or manually update to the latest) and then release v1.0.0 on npm?

It's a really great idea to add LoDash method to the libx collection!

I think that a sorting method also should be a 'must' when we are talking about collections. LoDash has at least 2 methods to do that: sortBy & orderBy, where orderBy is more complete because he allows to specify the sorting order.

Do you see some complexity to use LoDash orderBy method?

https://lodash.com/docs/4.17.4#orderBy

Hello and thanks for this lib!

I've implemented something similar in my projects before and there is one big problem I've encountered. And it's with cross-store communication and setting up reactions in store's constructor methods.

Say you have 2 stores: A and B and inside your RootStore you create A store first. Now you get the reference to the instance of RootStore inside A's constructor, but you don't have a reference to the B store because at that point it doesn't exist yet.

How do you set up mobx reactions in A store that would depend on observables from store B?

I've ended up splitting creation and initialization of stores into 2 phases: constructor and init(meaning that first all stores are created and then all init methods are called on those stores) so inside init method of any store you have access to any other store and by convention we only set up reactions and otherwise reference other stores only inside those init methods.

How do you solve this problem in this library?

Use browserslist field to identify targeted browsers and automatic polyfill (not sure if there is a feature for that in TypeScript, but this is supported by Babel)

https://github.com/you-dont-need/You-Dont-Need-Lodash-Underscore

Hi,
Great lib so far!
I've read the README through and through and did not find anything about removing references.

Let say I have model A that created a model B and is referencing it in a computed property.
If A is removed, I want to make sure B is removed as well.

Is it possible? What did I miss?