Move to monorepo

[pavanpodila]

This will house various packages and make it easy to maintain:

Core

• mobx.dart (primary project)
• flutter_mobx (flutter bindings)
• mobx_generator (will contain code generator. Name is not final)
• flutter_mobx_hooks (hooks driven state management)
• website (public facing website, possibly hosted on github.io.)

Experimental

• mobx_observatory (experimental tool for visualizing the internals of MobX as it runs an app. This will be possible if we run a tiny web-server with web-socket that posts messages when various events occur inside MobX. It will also expose a localhost url that can be opened in Chrome to see the visualization. The visualization itself can be built with React 🤓. Think of this as the Observatory for MobX )

[rrousselGit]

I can potentially help for the flutter sides if needed. 😄

[pavanpodila]

Awesome @rrousselGit. I think this will speed up the move to monorepo as well. Ideally this code should live in the flutter_mobx_hooks project.

🤔 One other option is you can create the hooks code in a separate folder to get started. Once you have it working, we can extract it out to flutter_mobx_hooks. 🤔

[katis]

I can try to tackle this after work. mono_repo seems to be used by few projects.

[rrousselGit]

the issue with mono_repo is that is doesn't support flutter yet. I made a PR so that it won't crash, but it doesn't automatically download the Flutter sdk and run commands.

This is still doable by using command: in the yaml, and manually filling the gap though.

[katis]

@pavanpodila I've tried various approaches to make a mono repo, but either I can't get them to work, or they seem to bring more complexity than they're worth.

I say we create separate repositories for the packages for now, and see about a monorepo later.
Is it possible to add the repositories to mobxjs org?

[pavanpodila]

Do we even need separate repositories ? I suggest we keep the packages together under this repo and publish separately? I think maintenance is much easier if they are all together. At least at this stage where the packages are still maturing. What say?

[pavanpodila]

And agree about skipping the whole mono_repo dependency. We can add that later if it works out.

[katis]

You are of course right about the ease of maintenance from a cross-package point of view, but Travis configuration becomes a problem. With a single package repository the ready made configs of language: dart work well, but with multiple packages you have to write the scripts yourself. I'm not that familiar with Travis, so I couldn't figure out how the config would work. If you want to try, you're welcome, but I'm out of ideas.

[rrousselGit]

I would heavily suggest to send a mail to Flutter for this.

Because the community has been small until now, Flutter team haven't really noticed the monorepository issue.

[pavanpodila]

I think in principle the monorepo idea is good, so we can keep the two packages (mobx and flutter_mobx) together. If it means replicating the Travis scripts, I'm ok for now as there are only two packages. I can do the duplication but it is not that hard, just a matter of fixing the paths in travis.sh.

Let's get flutter_mobx working for now removing any mono_repo boilerplate? I'll help out with the travis.sh scripts when you are ready.

Also as @rrousselGit suggested, we should get in touch with Flutter to share our specific issue? @katis could you raise an issue detailing where you found problems ?

[pavanpodila]

On a separate note, @rrousselGit can you take a look at the PR (#34) to see if there are any obvious fixes?

[katis]

That PR is probably not that useful starting point atm., I made a bit of a mess of it

[rrousselGit]

I don't see anything special. Looks good :)

[katis]

This is done.