Server-side filtering on _id is allowed by default

Since the _id field is published by default, with this release it is also filterable by default. It can still be explicitly excluded in the server-side settings.

Disable row reactivity option for ReactiveTable.publish

This release adds a disableRowReactivity option to the server-side settings. If you set both this and the disablePageCountReactivity option to true, it will completely disable reactivity.

Chinese (traditional) translation

v0.8.33

Version 0.8.33.

Fix server-side filtering on nested array filter

This fixes a bug that made it impossible to use a custom filter on an array field that was projected on the server side. For example, if you have an item like {a: [{b: 'c'}]}, you can project fields inside the array when publishing on the server by using fields: {"a.b": 1}. However, if you wanted to filter on a particular item in the array, you couldn't use a field a.0.b since it didn't match the server-side projection. This change allows filtering on any array index if the array field is projected.

Ensure custom filter fields are always set on creation

This fixes a bug introduced in 0.8.29 where calling new ReactiveTable.Filter(filterId, fields) sometimes wouldn't set the fields correctly.

Server-side disablePageCountReactivity option

If you don't need the page count to automatically update, using the disablePageCountReactivity option will improve performance of server-side ReactiveTable.publish.

Fix filter bug

This release fixes a bug that would sometimes cause the filter's reactive dependency not to be initialized correctly, so that typing in the filter box wouldn't work, but sorting or pagination changes would make it start working again.

Sorting with column header template

This fixes #361 - Using a template with HTML elements as a field's label would break clicking the label to sort.

ReactiveVar settings and server-side publishing

When using server-side publishing and ReactiveVars for table state in the settings (rowsPerPage, currentPage, sortOrder, or sortDirection), changing the ReactiveVars will now update the subscription correctly.

Stop subscription when template is destroyed

This fixes a bug where the package's internal subscriptions for server-side collections would persist after the table template was destroyed.