I’ve started to experiment a specific Meteor’s dataprovider (1) for react-admin, for example getList works fine for users, but I’m unable to get it work with another collection !
I have also been working on a meteor data Provider for react-admin (method calls only so far, so not reactive). It turned out to be a bigger job than I expected, but only because I was trying to make it a project (eventually). I got it ??working?? with a minimal test data set for react-admin v2.9.7 but the lag before the provider was called was about 15 seconds. Not great, but I figured I would track that down later.
Now that I’ve upgraded to v3.0.1 the delay is about 2 minutes. I can’t be completely certain, but I think the processing which is causing the delay has to do with initialization of the react-admin/redux sub-system: the server comes up quickly, but the client side doesn’t. I only see Meteor.start() being hit after the 2mins have elapsed.
Before I go too far down this path, I wanted to ask: are you experiencing these kind of delays before the UI for react-admin comes up?
@sabativi yes I’ve implemented a specific search filter for my needs on getList, added getOne, getMany, delete, deleteMany. Missing create (for Users), update, updateMany…
Would you like to verify and finish this task ?
Is there other people wanting to participate ? @umbralimi ? someone from marmelab ?
I suggest an online meeting : demo of current work done, mob programming to finish the work and publish a usable repo ?
Hey, thanks for your quick reply.
Yes I will be more than happy to continue the work, do you have some kind of github repo that I can contribute to and test the connector