v1.6.0
Vuetable-2 v1.6.0
- You can now display icon (via CSS class) in column title. See doc here
- Vuetable now watch changes to
api-url
prop so that the data gets automatically refresh, thanks to @c0defre4k for PR #58. - Replace
vue-resource
withaxios
, thanks to @ lmj0011 for PR #65 - Fix
els.forEach
compatibility issue that caused error on browsers other than Chrome. Thanks to @bajian for PR #66. - Deprecate
row-class-callback
prop forrow-class
prop row-class
prop is now also acceptingFunction
, thanks to @c0defre4k for PR #82.- Add CDN bundle to
dist
directory, thanks to @cristijora for PR #94. - Fix problem with browserify, thanks to @pajtai for PR #100.
- Move most of the CSS related icon classes into
css
prop. - Support data array via
api-mode
(which istrue
by default) anddata
prop.
The default behavior (and still is) of Vuetable-2 is working with API endpoint. Theapi-mode
was added to allow using client side data array with Vuetable. However, all functionalities related to server side are disabled, e.g. sorting, paging, page sizing, etc. Related methods and properties will be marked if they will work on ApiMode only or not. sortFiled
is now passed to the__component
. Thanks to @SimplyCorey, Close #68.- Log error to console when loadData failed.
this will help identifying the problem easier when there is problem requesting data from the server - Rename
sort-icon
tohandle-icon
, renamecss.sortHandleIcon
tocss.handleIcon
- New method:
resetData
This will set bothtableData
andtablePagination
tonull
and firevuetable:data-reset
event. - New event:
vuetable:data-reset
This event will help improve better coordination with pagination and pagination info components when the data has been reset tonull
. - New prop:
render-icon
-- allow overriding how the icon tag is rendered - Thanks the following contributors for helping with documentation
- Special thanks to @cristijora for helping out on the questions in the issues and improving the CDN bundle, PR #123.
- Sorry if I missed out anyone, please do not hesitate to let me know.
Note
I'm still new to semantic versioning and I learn as I go with this project. That's why the version number is a bit strange.