Repository navigation
Roadmap to version 6.0 #1297
Replies: 10 comments 14 replies
|
@6pac opening this initial list of things to address for our next major v6, feel free to modify and/or ask questions if you have any. The next thing that I believe is required is to replicate the "use Hidden columns only", I've done this change in my own repo 6 months ago and it's basically you who started it via the column definition I pushed a new patch version now and also created a new brach |
|
Looks all good to me. The only issue might be dropping the IIFE - I think a number of consumers might still need this. I think it's OK to drop it if we offer a patch or add-on to provide that functionality. CJS is long gone, so I don't think we'd have problems there. As I've mentioned previously - I have some major changes waiting in the wings (DataProvider) to feed in from my private fork, but I don't know if they are going to be worth doing to the main repo, perhaps I'll keep them as a personal patch. I think it's best to leave that for a later release and get things stable for this major relase with the features we have. |
|
OK, I'll kick off the docs generation. Re IIFE, I think perhaps release a PR getting rid of everything but ESM and I'll see if I can put together a regex engine to transform it all into IIFE complete external to the project. |
|
Docs are up. One other thing, I have been wondering if we should move row autosizing into a plugin, since we have the legacy way, my way and your way at the moment. I think it would be easy to do, then we could have the three alternatives available in the plugins folder but not part of core. |
|
no probs, it was just a thought I've had a few times. Seems like a good time to implement it in case it is breaking. Fine to wait, I'm just really happy this is all happening. |
|
@6pac so I decided to merge the |
|
Great that you've released V6, but shouldn't that list of breaking changes be much, much, much bigger? |
|
doing that. You have a migration guide apparently, but did it get wiped when we added the documentation? Can't find it. |
|
Actually, it is there under the in-depth section. I might move it to its own section though. Claude did find a number of issues with the migration doc as well, so I might get it to post them here so you can check them over before it does anything more. |
|
@ghiscoding, 6pac asked me to compare 5.20.2 with 6.0.0 to find every breaking change, since the release notes list only four. I compared the two tags directly: package.json and the build, the exports, the public and protected members of the grid, plugins and controls, the option defaults, the generated CSS classes and the SCSS. I didn't rely on the commit messages, and I re-checked the riskiest findings against the code. Nothing has been changed yet: 6pac wants you to look these over first. Problems in the migration guideThese are the parts of
Possibly unintended:
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
SlickGrid Roadmap to v6 (breaking changes)
and standalone script (IIFE)and keep both IIFE and ESM buildshiddencolumns onlyhiddenproperty and always keep all columns #1299rowTopOffsetRenderType, requires to replicate these PRs:autoHeight?autoHeightgrids #1351autosizeColumns()and to provide similar API signature as SlickGrid I have this code:scrollRenderThrottlingor setting it to0for improving scrolling perf (Codex calls it the "fast vertical scroll blanking")upgrade to TypeScript 7.0typescript-eslintdoesn't support TS7 yet but probably will when TS7.1 ships later this year (see Enhancement: Use TS 7 (tsgo / typescript-go) for type information typescript-eslint/typescript-eslint#10940)FieldTypeenum, it isn't used in here (copied by mistake from Slickgrid-Universal interfaces when we migrated to TypeScript)migrateSlickCompositeEditormodal from<div>to<dialog>@deprecatedcode--alpine-...variables prefix with--slick-...to align with Slickgrid-Universalslick-...instead ofalpine-...#1317.ui-...CSS classes and keep only.slick-....ui-...CSS classes #1313slickGrid.tsrename functiontriggertotriggerEvent()and make it public so it aligns with Slickgrid-UniversaltriggerEvent()and make it public #1315dist/folder from GitHub, we no longer need it for the Examples to workinvalidColumnPinningPickerCallback), I think we could keep only 1 aserrorCallback: (msg) => alert(msg)and reuse it for all possible error messages (e.g.invalidColumnPinningWidthMessage)after release
All reactions