This repository was archived by the owner on Oct 2, 2018. It is now read-only.
Releases: bigdatr/bd-stampy
Releases · bigdatr/bd-stampy
v0.6.4
v0.6.3
Added QueryStringProvider
- Added a QueryStringProvider higher order component which allows you to get and set the query string object by providing a child component with props, using react-router. It also allows for array parameters containing any characters.
- Fix spelling mistake of onPaginate prop on DataTable, but still allows old 'onPagingate' spelling for compatibility with older components
Misc improvements
- components/Table.jsx can accept and children
- bug in mixins/FormMixin.jsx fixed
- utils/Paginate.js can now accept an immutable list in addition to arrays
Removed Lodash
Have removed all lodash and replaced with equivalent functionality, except:
- Bug fix in AutoRequest to prevent immutable props from being turned back into vanilla JS.
FormMixin.FormMixin_getData now clones state deeply instead of shallow, which is safer and I couldn't find any evidence of the 'shallowness' of the clone being exploited in any of our apps. - Table is deliberately dumbed down now for use with simple static data, and any DataTable style functionality is purely in DataTable. Apps upgrading from <0.5 should update their usage accordingly.
- History.loadUrl now behaves like the comment above it suggests it should, returning true or false rather than arbitrarily returning this.handlers. Could not find any evidence in any apps that the return value of loadUrl is actually used for anything.
DataTable bug fixes, added ComponentClassNames.js
- DataTable now uses new Pagination properly
- DataTable no longer uses lodash
- utils/ComponentClassNames.js created to easily apply Spruce class names to components
Pagination updated
Breaking changes
- ammount prop renamed to amount
- page number now starts from 1 and not 0
Files affected
- components/Pagination.jsx
- utils/Paginate.js
Component removal deprecation warnings
Component removal deprecation warnings