Amy Slagle

I released a new version (0.8.27) that should fix this. Try it again and let me know :)

I'm not sure why meteor wouldn't pick up the update, but you can edit .meteor/versions directly to make sure it uses the right one.

If you have the search results already, there's not really any reason to use ReactiveTable.publish. I'd continue passing them in the way you were before. If you really want to...

No, sorry. And unfortunately I don't think you could implement it without modifying the package.

I'd suggest setting the filters before the table initially gets them. You should be able to put the initialization in a Template.onCreated. They won't be used until the table template...

Not sure what you mean. You can set hidden to true on an individual field, but you do have to include all the fields in the array to change settings...

Yes, reactive table works with cursors as well as collections, so you can use collection.find(selector) as the collection argument to the table.

Oh, I see. For server-side filtering you're right, you have to use the name. You can pass in the selector to ReactiveTable.publish on the server (ReactiveTable.publish(name, collection, selector)) if you...

I wanted to support cursors on the server-side, but I couldn't figure out a way to add pagination and filtering options to an existing cursor. You have to pass in...

`showFilter: true` in the table settings will restore the default filter box, it's removed by default when you use your own filter.