You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4. we only have 1 preheader, so this mean we can't use simple features that use the same preheader because of the conflicts (DraggableGrouping/HeaderGrouping)
5. possible use of Web Worker for Export Services to avoid blocking main thread while downloading
gave it a try but it doesn't look feasible since Web Workers don't even work with binding scope, it only works with local code that has no connection (scope) to the outside which seems impossible in here since we need to use the SlickGrid/DataView variable bindings to read every row and all kind of other things
6. Infinite Scroll for Backend Services (see Ag-Grid Infinite Row Model)
7. try to use SortableJS ESM import and see if it helps with build size
import Sortable from 'sortablejs/modular/sortable.core.esm.js'; (see SortableJS Getting Started)
make sure Column Reordering and Draggable Grouping also still works
currently makes 2/3 of unit tests to fail in PR perf: use SortableJS ESM import to save 1kb #1621 because Jest only supports CJS, so I'll cancel this for now but might revisit if migrating to Vitest with full ESM
EDIT: I gave it another try after migrating to Vitest and sortable.core.esm.js doesn't play well with current Types @types/sortablejs because the names don't match. Considering that this is a pain to get proper Types, I think I'll just keep current approach and 1kb bigger is not that much of a difference. The hope is that one day, SortableJS offers better ESM support (but I won't put much hope on this happening anytime soon sadly)
8. drag rows between 2 grids and/or drag row to outside container like a recycle bind
1. between 2 grids (won't do since this requires a new plugin and no one ever requested this feature), alternatively any user could simply create their own plugin themselves.
11. custom pagination is not currently replaceable by the user, but it probably should be eventually to be fully customizable
12. add silenceWarnings to all ports in next version only
13. I think that GroupingAndColspanService should be renamed to HeaderGroupingService since there's nothing related to colspan (the colspan was actually meant to represent that header can span across multiple columns, but SlickGrid always called it Header Grouping, so let's use that name instead in the next minor version)
next potential major version ideas
20. drop CJS? Yep we'll schedule it for our next major release around Node 18 EOL
22. possibly switch to column hidden property, which we tried in the past via this SlickGrid PR. It could be an issue in ColumnPicker/GridMenu, requires more in depth testing
23. drop Node 18 and upgrade dependencies that require Node 20
24. remove internal deep copy of GridOption and allow user to update any option by reference
28. perhaps @formkit/drag-and-drop might be a good alternative to SortableJS which doesn't provide an out of the box ESM (they provide sortable.core.esm.js but it breaks @types/sortablejs, which isn't ideal)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Below is a list of ideas, there's a good change that it will never come to fruition but I'm just listing them as possible ideas anyway
possible use of Web Worker for Export Services to avoid blocking main thread while downloadingtry to use SortableJS ESM import and see if it helps with build sizeimport Sortable from 'sortablejs/modular/sortable.core.esm.js';
(see SortableJS Getting Started)sortable.core.esm.js
doesn't play well with current Types@types/sortablejs
because the names don't match. Considering that this is a pain to get proper Types, I think I'll just keep current approach and 1kb bigger is not that much of a difference. The hope is that one day, SortableJS offers better ESM support (but I won't put much hope on this happening anytime soon sadly)between 2 gridsand/or drag row to outside container like a recycle bindbetween 2 grids(won't do since this requires a new plugin and no one ever requested this feature), alternatively any user could simply create their own plugin themselves.stop using Jest Global types, see this potential PR of another project to handle itMigrate to Vitest insteadsilenceWarnings
to all ports in next version onlyGroupingAndColspanService
should be renamed toHeaderGroupingService
since there's nothing related to colspan (the colspan was actually meant to represent that header can span across multiple columns, but SlickGrid always called it Header Grouping, so let's use that name instead in the nextminor
version)next potential major version ideas
major
release around Node 18 EOLrowTopOffsetRenderType
and usetransform
in nextmajor
releaserowTopOffsetRenderType
grid option to use "transform" #1650hidden
property, which we tried in the past via this SlickGrid PR. It could be an issue in ColumnPicker/GridMenu, requires more in depth testingonItemAdded
,onItemDeleted
,onItemUpdated
,onItemUpserted
sortable.core.esm.js
but it breaks@types/sortablejs
, which isn't ideal)Beta Was this translation helpful? Give feedback.
All reactions