Field Function fails for first field about reactive-table HOT 4 OPEN

You're right - there was a bug. It seems like the changes to mongo in meteor 0.8.1 no longer allow passing an undefined argument to find, and I accidentally had one. I don't understand why it only happened with the first field though.

The error message I was getting wasn't exactly the same as yours, but I think it's fixed now - try the latest version. Thanks for reporting this and glad you like the package :)

from reactive-table.

HA! And here i spent my afternoon implementing a workaround so I could just get the correct data to the objects in the first place. It's a good bug- made me learn how to do transforms on a collection.find() properly.

Also, these could be other issues but two things i noticed (minor):
-The Ascending / Descending icons are backwards (i think, maybe i'm crazy)
(Scratch that i'm totally nuts.. just checked again.)
-A column will stop sorting if you use a SafeString.

Thanks again!

from reactive-table.

The columns should still sort if you use a SafeString, but they'll sort based on the html, not the value. Are you seeing something else?

(The sort arrow direction is confusing, but ascending = down looks right to me and is consistent with font awesome. I did find this saying they should be the other way, it's not just you :) )

from reactive-table.

I'll check the SafeString sorting out this weekend if I get a chance. As for the arrow direction- I look at it graphically- a downwards facing arrow (for example a capital V):

V

Is bigger at the top, and smaller at the bottom- so it makes me think, larger values at the top, smaller at the bottom.

It is funny that it's still debated in 2014 LOL but I guess it's all about preference.

from reactive-table.