vincjo

Yes, it is possible. For implementation, you'll need to use the 'create**Advanced**Filter' method instead. ```ts const filter = filter.createAdvancedFilter('datacenter') const selected = filter.getSelected() ``` Then, in markup side: ```svelte filter.set('data1',...

Hey, thx for your suggestion. I understand your point but can't figure out how we could achieve this. For now I just added: ```diff if ($filters.length > 0) { $filters.forEach((filter)...

#98

I guess i should create a new project with a `npm i @vincjo/datatables` and test it properly. Thanks for the warning, will fix it for sure

Thank you very much for warning. I still need to work on handling CSS. The goal is to keep the current behavior but make CSS overwriting easier. `2.0.0-runes.32` is more...

Using `import ./style.css` in script tag instead of `@import` in style tag seems to fix the issue. Fix: [`2.0.0-runes.38`](https://github.com/vincjo/datatables/blob/runes/CHANGELOG.md#200-runes38---2024-10-04)

Hello, Currently it works with litteral paths such as `row.node.customerNo` or `row['node']['customerNo']` I parse the callback with a string convesion + regex to retrieve the path of the nested value...

Finally, I didn't find a way to reconstruct the path and highlight filter results when Field definition contains variables. For highlighting, we'll need to use a callback in `ThFilter` instead:...

Yes, indeed, data must be updated using `table.setRows(new_data)`: The raw data is deep cloned, so no longer shares any state with the original object, even if declared as a $state...

Hi, Thanks for the question. I'd recommand to craft your own components for cutomization requirements. The components bring too much style opinion to provide a very large reusability. There are...