Dynamically created collections fail about reactive-table HOT 5 OPEN

Interesting. I've never tried reactive-table with fast render so that could be the problem. I'll have to test that out.

As a workaround you should try passing in some fields like this. That line that's throwing the error was meant to make it as quick as possible to set up a table, so if you don't specify the fields you want as columns, it takes the first item from your collection and uses its fields. If you specify them, that part of the code gets skipped.

from reactive-table.

Thanks, I'll have a go and see what happens, otherwise I believe the issue is the collection isn't ready yet. I realised the case is the same as this. I'll see how I get on and report back. http://stackoverflow.com/questions/17728386/meteor-findone-query-returns-undefined-in-one-template-helper-in-other-template

from reactive-table.

Hi, I tried adding fields and it just fails on line 56 with the same problem.

reactiveTable error: argument is not an instance of Meteor.Collection, a cursor, or an array reactive_table.js:56
Object {_id: "HECii3o4MEYGzGBAC", type: "test"} -- yet I can access the object client side
this is using settings as well

from reactive-table.

Update, I got it to work but it still gives me an error in the console
error: argument is not an instance of Meteor.Collection, a cursor, or an array

without settings it crashes
Exception from Deps recompute function: TypeError: Object.keys called on non-object

Can you tell me if Reactive-table is trying to do this on both server and client?

this is the project https://github.com/mikey0000/meteor-api

from reactive-table.

Glad you got it working. I'm curious how you fixed it, I did manage to reproduce the error with a collection created in Meteor.startup but I haven't figured out what the problem was.

I'll add some error handling for an empty collection with no fields to prevent that TypeError. reactive-table is currently client-side only, it doesn't do anything on the server.

The error message in the console is probably because the collection hasn't been created yet when it's passed in, but that shouldn't be a problem. Once the collection is created, meteor should re-render the template and the table will update.

from reactive-table.