Future Ideas and possible features #1527
ghiscoding
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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 binbetween 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)"peerDependencies": { "react": ">= 18.0.0" }
fetch-jsonp
with native Fetch? Maybe this SOnext potential major version ideas
major
release around Node 18 EOLrowTopOffsetRenderType
default value fromtop
totransform
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
i18next
to v24 andi18next-http-backend
to v3 (same for Aurelia-Slickgrid)sortable.core.esm.js
but it breaks@types/sortablejs
, which isn't ideal).set()
method (see comment)node-extend
from utils/nodeExtend to a separate npm org for utils, maybe@universal/node-extend
or something similar, the reason being that the officialnode-extend
repo have no intention of going ESM as per this node-extend issue and I want to move it outside of the Slickgrid-Universal world so that other users can take advantage of an ESM package (or maybe even myself in projects not requiring SlickGrid)await import(plugin)
. I'm guessing that ViteJS is potentially doing similar with SASS which doesn't work until you npm install SASSframeworks
folder in the workspace and provide optional install for each frameworks in readme viapnpm install --filter
- will require GitBook in Monorepo changes / use our "...-demos" repos for live demos
frameworks
folder is implemented, we could align all ports to 9.x version (because Angular/Aurelia ports are already at 8.x)whatwg-fetch
with native NodeJSfetch
, probably requires Node 20.x and higher (requires Node 18.13+)Drag-and-drop test code (click to expand)
Test Code
Beta Was this translation helpful? Give feedback.
All reactions