Releases: geodask/svelte-reactive-table
[email protected]
Patch Changes
- 70b932a: chore: update packages
[email protected]
Minor Changes
-
0a8e031: feat: add filtering plugin
This update introduces a flexible and easy-to-use filtering system that supports multiple filter types and intelligent value matching.
Key features:
- New
reactiveFilteringplugin for flexible data filtering - Intelligent filter matching: exact values, arrays for IN operations, and custom predicate functions
- Built-in string filtering with case-insensitive contains matching by default
- Configurable case sensitivity option
- Comprehensive filter helpers for common patterns (range, startsWith, endsWith, exactText, not)
- Simple state management with reactive filter tracking
- Clean API:
setFilter(),setFilters(),removeFilter(),clearFilters(), andgetFilter() - Full TypeScript support with proper type inference and safety
- Seamless integration with existing plugin architecture using
table.use(plugin)pattern
- New
[email protected]
Minor Changes
-
99fff82: feat: implement plugin architecture for table features
This update redesigns how table features work by introducing a standardized plugin system. Features like pagination, sorting, and column visibility are now implemented as plugins with a consistent interface.
Improvements include:
- New plugin system with
table.use(plugin)method - Enhanced pagination state with
hasNextPage,hasPreviousPage,isFirstPage,isLastPage, andpageItemRange - Better TypeScript types for improved type safety
- Standardized plugin lifecycle with init and cleanup methods
BREAKING CHANGES:
- Plugins must now be attached to tables using
table.use(plugin) - Plugin state is accessed through
table.plugins.[pluginId].state - Navigation methods are now renamed to
goToNextPage,goToPreviousPage,goToFirstPage,goToLastPage
- New plugin system with
[email protected]
Patch Changes
- a8308bd: refactor: small improvements
[email protected]
[email protected]
Minor Changes
-
8df363c: feat: add column visibility as an opt-in feature
- Introduced new
reactiveColumnVisibilityfunction - Added ability to manage column visibility (when enabled) through the table's
columnVisibilityproperty with methods for toggling, showing, and hiding columns
BREAKING: Column visibility API has changed -
visibleproperty has been removed from column definitions, visibility methods are now moved to thecolumnVisibilityobject, and some property names have been changed - Introduced new
-
5b60ac5: refactor: simplify API by exposing paginated rows through table.rows and prepare for future features
This refactoring improves the pagination API by moving row management from the pagination component into the core table. Instead of accessing rows through
table.pagination.rows, users now consistently usetable.rowsregardless of active features.Key changes:
- Refactored internal pagination architecture to better separate concerns
- Created a more unified and intuitive API for accessing table rows
- Maintained all pagination functionality and state management
- Updated documentation and examples to reflect the new approach
BREAKING CHANGE: Applications using
table.pagination.rowsmust now usetable.rowsinstead.
[email protected]
Patch Changes
- 656f74a: fix: remove
$effectfromreactiveTablefunction
[email protected]
Patch Changes
- ecaa473: fix: small issue with reactivity
[email protected]
Minor Changes
-
bd6bb1b: refactor: make pagination optional with improved TypeScript API
- Make pagination completely optional through a new options-based API
- Add TypeScript generics to provide proper type safety with or without pagination
- Introduce
TableOptionsinterface for configuring table features - Improve public type exports for better developer experience
- Update examples to demonstrate both basic tables and tables with pagination
- Enhance type organization for better code documentation
BREAKING CHANGE: Introduced new options-based API for table configuration that changes how tables are initialized and configured.
-
f4ba175: feat: add modular pagination support
- Add new
reactivePaginationAPI for configurable table pagination - Change table API to use composition pattern for pagination
- Export pagination types and functions in public API
- Update examples to demonstrate the new pagination approach
BREAKING CHANGE: The table API signature has changed. Pagination is now provided through a factory function instead of configuration options directly on the table.
- Add new
[email protected]
Patch Changes
- 2c6254b: refactor: remove examples from lib directory