idibidiart

@dsibiski so your ModalWithNavigatorExample works great, and I'm wondering what are the issues with it that would prompt further work or different approaches...? Curious!! :) Thanks!

Oh, yeah makes sense @dsibiski @bnookala :) In fact, the best way I could help beyond my view on the architecture of an "Objective-C Managed" hybrid app, which I had...

I'm adding a way for users to avoid capturing certain URLs. But both delete and grouping would be good to have. Delete is straight forward. But delete and grouping together...

Hi Parin I've added ability to delete individual items in 0.0.5 I've also made a few fixes (regressions in 0.0.2 were fixed in 0.0.3, and interruptible result streams were added...

One more: https://github.com/idibidiart/react-native-responsive-grid this is allowing me to build complex layouts at 20 ,ins per screen vs 2 hours per screen when done without it... it's based on work by...

I think 'params' is overloaded. It contains 'provider' and 'token' which should be split up under a 'context' argument It also contains 'query' in case of find() It also contains...

Or id argument can be string or array so: id (string or array) query (object) context (object) params as it is is too overrloaded and hard to remember the details

(marcfawzi here) I've not read the entire thread but I assume that we'll be able to use a database per service (in the Micreoservices architecture having this separation is crucial...

Yeah exactly what I meant. I tend to think that segregation of services where each service has its own db is a sure way to force composition via the service...

@zapur1 that looks promising... I've posted a comment to get the discussion started