React tables

This is a redo of #1502. I have done some architectural restructuring so that the base Table React component is more generalizable, and I've changed the way components get mounted onto the view (originally was using the react-rails gem, but now going a more native route). Also deleted unnecessary .rjs files (for the original tables) and partials, as well as the students' populate route in route.rb (we now populate by sending an AJAX request to the same url, just requesting it in JSON).
Yup it's right. func is the key and the function is the value

On Aug 1, 2014 3:57 PM, Lawrence Wu <notifications@github.com> wrote:
> +        searchable: false
> +      }
> +      ];
> +
> +      // need to filter for each section
> +      var section_filters = [];
> +      section_filters.push({name: '-', text: '-', func: function(g) { return g; } });
> +
> +      for (var i = 0; i < this.props.sections.length; i++) {
> +        var filter = {
> +          name: this.props.sections[i].name,
> +          text: this.props.sections[i].name,
> +          func: function(group) {
> +            return (group.section == this.name);
> +          }.bind(this.props.sections[i])
> +        }

no, I believe this is correct
```javascript
var a = {
  f: function() {
    return 0;
  }
}
```
works as expected, while
```javascript
var a = {
  f: function() {
    return 0;
  };
};
```
results in a `SyntaxError`.

---
Reply to this email directly or view it on GitHub:
https://github.com/MarkUsProject/Markus/pull/1539/files#r15715670