Releases: aslagle/reactive-table
Fix Ukrainian translation
v0.6.11 Version 0.6.11.
Change direction of non-fontawesome sort arrows
This release switches the direction of the sort arrows when not using Font Awesome to match the ones in Font Awesome - up arrow for ascending, down arrow for descending.
Allow overriding default classes on th and td elements
This release adds a cellClass option to add class to the td elements, and modifies the headerClass setting to override the default of adding the field key as a class as well. If you're using headerClass and you want the field key as a class, you'll need to add it to headerClass explicitly.
It addresses #161 - using keys that matched bootstrap classes could add unwanted styling to the table. Set headerClass and cellClass to empty strings to prevent this.
Update server-side collection when user changes
This fixes a bug (#164) with server-side publishing that did not rerun the collection and selector functions when the logged-in user changed.
Preserve _id from server-side publishing
This release fixes #151. Calling ReactiveTable.publish from the server will no longer modify the _id of the published documents.
Reactively add new fields to table
This release fixes #156. Fields can now be added to the table settings, and the table will reactively update. If you're using the columns toggles button with dynamic fields, each field must have a unique fieldId.
Polish translation
v0.6.5 Version 0.6.5.
Table column header templates
The label
option to set a column header can now be a Blaze Template, as well as a string or function. Use labelData
to set the data context of the template.
Change Meteor.Collection to Mongo.Collection
This replaces the deprecated Meteor.Collection with Mongo.Collection internally and in error messages. No changes in functionality.
Allow special characters in filter text, and enableRegex option
This release changes the default behavior of filtering to automatically escape special characters before creating a RegEx. This means that special characters can be used in normal filter text, and server-side filtering isn't vulnerable to RegEx DoS attacks. If you want to let users enter a RegEx as a filter, you can set the enableRegex option to true.