v7.6.1

7.6.1 (2024-04-01)

Quick Info

This release will now work with multiple tooltips on the same cell (e.g. multiple buttons with icons like the "Action" column in Example 35).

Bug Fixes

• allow multiple tooltips per grid cell (#1176) (8fbf543) - by @ghiscoding

---

Installation

Please remember that all packages of @slickgrid-universal (v4.6.1) and Aurelia-Slickgrid (v7.6.1) must be updated at the same time and they will always get bumped on the same day to avoid any upgrade issues. You can also consult the Versions Compatibility Table - Wiki

please remember that Slickgrid-Universal monorepo now contains the biggest portion of the code (~90%), so most of the commits are now happening on that side.

1. review the Slickgrid-Universal changelog
2. and the Aurelia-Slickgrid changelog (above)

v7.6.0

7.6.0 (2024-03-23)

Quick Info

This release upgrades multiple-select-vanilla package, that I also maintained, with a much more modern UI with the use of SVG icons. The SVG icons in that external lib are now also written in pure CSS which helps for Dark Mode (in that mode, the primary color for checked icon is a lighter version of the primary color). Note however that the SVG icons in Slickgrid-Universal are not yet pure CSS since that would introduce breaking changes in Slickgrid-Universal (a new major version will be pushed later on to address that).

⚠️ Custom Editor/Filter should not be newed

Please note that Custom Editor/Filter should never be newed even though the documentation previously said otherwise, this has been corrected in this release via an update on the Column interface, so if you have any of them instantiating that way then please fix them to avoid build errors.

// same goes for Custom Filter
editor: {
  // reference your custom editor class without instantiating it
-  model: new CustomInputEditor()
+  model: CustomInputEditor 
},

⚠️ internalColumnEditor is deprecated and no longer needed

Note that in the past, SlickGrid and Slickgrid-Universal/Aurelia-Slickgrid were using 2 different references for editor. The original SlickGrid was using editor as a Class to be later instantiated (e.g. Editors.longText) but that wasn't very convenient for the end users (you). For that reason I decided a long time ago to take this editor and reassign to another ref named internalEditor and then SlickGrid kept using editor (read from editor.model) and whenever the user wanted to read the SlickGrid editor after the grid was initialized, the user would have to get it from column.internalEditor (because after the initialization editor is SlickGrid's internal editor class not the one provided by the user), but that was so damn confusing... but now that Slickgrid-Universal is a standalone (no longer relying on 6pac/slickgrid) I decided to get rid of this confusion, so with this new release the editor remains the same to the user but the one used by SlickGrid just got renamed to editorClass. So in summary, editor is the same for the end user and editorClass is what is defined by model: Editors.longText and the internal ref swap that Slickgrid-Universal/Aurelia-Slickgrid was previously doing is no longer needed internally. Below is an example of when that would be in use

// previously, to add an item to the editor/filter collection 
this.columnDefinitions = [{ id: 'complexity', editor: { model: Editors.singleSelect, collection: [{ value: 1, label: 'Simple' }, /*...*/ ]; }];
// then adding an item would require to read `internalColumnEditor` 
// after grid init, our `editor` became `internalColumnEditor
- const complexityEditor = this.columnDefinitions[0].internalColumnEditor; 
// BUT with this new release, adding a new item to the collection is as simple as 
+ const complexityEditor = this.columnDefinitions[0].editor; 
complexityEditor.collection.push({ value: 9, label: 'Hard' });

// and if you want to read the SlickGrid editor, you would now use
this.columnDefinitions[0].editorClass; // which is the same as `editor.model`

Bug Fixes

• Filter model is now FilterConstructor and shouldn't be newed (#1169) (de97e6c) - by @ghiscoding
• hide Toggle Dark Mode from Grid Menu by default (#1167) (f9be216) - by @ghiscoding

Features

• rename SG editorClass & deprecate internalColumnEditor (#1168) (bb958ff) - by @ghiscoding

v7.5.0 - Dark Mode

7.5.0 (2024-03-05)

Dark Mode ✨

This is probably a UX change that many users will be happy to start using, however there are a few important notes to be aware of as shown below.

• Dark Mode must be enabled via a darkMode grid option, it will not auto-detect the color scheme from the browser (you can however easily do it yourself). There are a couple of reasons as to why it was created as a grid option, it's mostly related to the fact that a few features in the lib require the creation of certain DOM Elements that are appended to the body (e.g. ColumnPicker, GridMenu, LongTextEditor, CompositeEditorModal, ...) and it requires extra code in place that SlickGrid will take care of it for you but can only work via a grid option, and for that reason it simply cannot be just simple CSS classes.
• SVG icon color are using a lighter gray by default, if you're using a Font family for the icons then that won't affect you however keep reading. As mentioned earlier, the SVG icons are using a light gray and that is because the same color must be used for both Light & Dark theme because at the moment the project will create the SVG with a fixed fillColor defined in SASS and once it is set, you cannot change it... you might ask, well can that be fixed in the future? The answer is Yes but... I did find that we can convert all SVG to pure CSS (using UnoCSS, by AntFu) approach but that will introduce some breaking changes and considering that I recently released a major version, I will wait couple more months to proceed with another major. Part of the breaking changes will be to drop support for Fonts and keep only SVGs internally in a future major release.
• the Dark Mode Theme was created using CSS variables, you might need to tweak some of these variables depending on your primary color, see Slickgrid-Universal CSS variables
• also note that I'm not a Designer, so if you feel that some colors are off then please contribute a PR
• for more info read the Dark Mode documentation
• you can see Dark Mode demo in Example 1, Example 24 and Example 30. All of these examples have a Toggle Light/Dark Mode button and the Example 1 also has the extra browser auto-detect Dark Mode the 1st grid only.

Also worth knowing that I also improved multiple-select-vanilla by adding a new feature to replace tabIndex by arrow navigation highlight. This feature will let you use the keyboard (up/down arrows or mouse hover) to navigate the select options and choose any of them (via Enter key) and all of that without losing your current focus (which is a lot better than using tabIndex). This new feature should be a lot more UX friendly.

This is pretty much completing the roadmap of all the features that I wanted to add to this library, this project started 7 years ago and I added a lot of features over the years.

Bug Fixes

• remove width style on grid container for CSP safe (03acd4a) - by @ghiscoding
• switch to isomorphic-dompurify for SSR support (#1164) (8ebeed2), closes /github.com/ghiscoding/Angular-Slickgrid/discussions/838#discussioncomment-8574215 - by @ghiscoding

Features

• add Dark Mode grid option (#1163) (2dc9e1d) - by @ghiscoding

---

Installation

Please remember that all packages of @slickgrid-universal (v4.5.0) and Aurelia-Slickgrid (v7.5.0) must be updated at the same time and they will always get bumped on the same day to avoid any upgrade issues. You can also consult the Versions Compatibility Table - Wiki

please remember that Slickgrid-Universal monorepo now contains the biggest portion of the code (~90%), so most of the commits are now happening on that side.

1. review the Slickgrid-Universal changelog
2. and the Aurelia-Slickgrid changelog (above)

v7.4.1

7.4.1 (2024-02-13)

Quick Info (Excel Export)

this new release is mainly targeting @slickgrid-universal/excel-export 🚀

We are migrating from excel-builder.js to a new fork Excel-Builder-Vanilla, the approach is a very similar to what I have done previously with multiple-select-vanilla, which is to create new forks of the project, and it is all about modernizing the project. This migration brings a lot of goodies by using this new Excel-Builder-Vanilla, it was rewritten in TypeScript, dropped Q (replaced by regular Promise), dropped Lodash (now uses native code) and finally replaced JSZip with fflate which itself also has an ESM build giving us Tree Shaking and it is also giving us better perf by using Web Workers (when using CSP, you might need to adjust your CSP rules). Why the switch? The reason is mainly to be ESM ready because technologies are evolving and ESM is really the future (the next release of ViteJS is also expected to drop CJS (CommonJS) support). The switch has other benefits too, the most noticeable one being the large decrease of its build size (that is because we dropped Q and Lodash).

You might be wondering, why not switch to a more popular library like SheetJS or ExcelJS? Well, believe or not, all these projects are still written as CJS with no foreseeable support to ESM builds. For that reason you cannot take advantage of proper Tree Shaking which mean that whoever rely on these projects, are in fact downloading their entire (large) library and all their dependencies. We certainly don't need all of these features (ie: we only want to build an Excel, not read it), all we need is to export to Excel and this is exactly what Excel-Builder-Vanilla is giving us in an ESM build and it is also extremely small since it's only targeting Excel file creation. 🏗️

Below are the migrating advantages to Excel-Builder-Vanilla

• rewritten in TypeScript (providing us with TS Types (d.ts)
• dropped very old dependencies that are no longer necessary (Q and Lodash)
• switched from JSZip to fflate (has ESM support with Tree Shaking and also better perf by using Web Workers)

No breaking change, the changes required were all internal and are totally transparent to the developers because the API is exactly the same as before, the only difference will be your build size decrease ;)

For a very customized view of what you can do with Excel-Builder, take a look at the Slickgrid-Universal Example 2, try to group by any column and then Export to Excel to see the very customized Excel output.

Note that if you had a JSZip path defined in your tsconfig.json, you can now remove it. that is because we migrated to fflate and it doesn't require any special config.

{
  "compilerOptions": {
-    "paths": {
-      "jszip": [
-        "node_modules/jszip/dist/jszip.min.js"
-      ]
-    }
  }
}

Bug Fixes

• update to latest Slickgrid-Universal v4.4.1 (44f933e) - by @ghiscoding
• demo: change trading demo full screen z-index lower than ms-select (6a89be9) - by @ghiscoding

Features

• ExcelExport: migrate to Excel-Builder-Vanilla (ESM) (#1157) (92e24a4) - by @ghiscoding

---

Installation

Please remember that all packages of @slickgrid-universal (v4.4.1) and Aurelia-Slickgrid (v7.4.1) must be updated at the same time and they will always get bumped on the same day to avoid any upgrade issues. You can also consult the Versions Compatibility Table - Wiki

please remember that Slickgrid-Universal monorepo now contains the biggest portion of the code (~90%), so most of the commits are now happening on that side.

1. review the Slickgrid-Universal changelog
2. and the Aurelia-Slickgrid changelog (above)

v7.3.1

7.3.1 (2024-01-27)

Performance Improvements

• decrease number of calls to translate all extensions only once (#1151) (97966a1) - by @ghiscoding

v7.3.0

7.3.0 (2024-01-21)

Quick Info

This release brings some great new features, the most interesting one was contributed by @zewa666 which is a new Row Base Editing. The Row Based Edit plugin allows you to edit either a single or multiple specific rows at a time, while disabling the rest of the grid rows. See our new Example 35 and new Row Base Editing docs.

Another great but smaller feature is a new reorderable column option to help lock a column in place (for more info see Slickgrid-Universal PR which include a small animated gif of the feature). Note that this feature is better when used with column position as first or last columns in the grid.

⚠️ Warnings

I did add and set reorderable: false to the following 4 plugins, they can all be overriden when instantiating the plugin via their respective options

• Checkbox Selector Column (Row Selection)
• Row Detail
• Row Move Manager
• Row Base Editor

Thanks

A huge thanks for @zewa666 contribution, the new Row Base Editing is most probably the biggest contribution made so far to this project. Thanks a lot!!! 🎉

---

Features

• plugin: new Row Based Editing (#1150) (9baf115) - by @ghiscoding

Performance Improvements

• resizer: autosizeColumns is called too many times on page load (#1148) (f4f64b3) - by @ghiscoding

---

Installation

Please remember that all packages of @slickgrid-universal (v4.3.0) and Aurelia-Slickgrid (v7.3.0) must be updated at the same time and they will always get bumped on the same day to avoid any upgrade issues. You can also consult the Versions Compatibility Table - Wiki

please remember that Slickgrid-Universal monorepo now contains the biggest portion of the code (~90%), so most of the commits are now happening on that side.

1. review the Slickgrid-Universal changelog
2. and the Aurelia-Slickgrid changelog (above)

v7.2.1

7.2.1 (2023-12-30)

Quick Info

This release brings some perf improvements and also completes the CSP Safe implementation, there was 1 last DataView function that was not yet converted to be CSP Safe and now it is (don't forget to use the new useCSPSafeFilter if you also use the DataView). There is also a new CSP Compliance documentation that you can read.
Lastly a few other small features and fixes were pushed, see below. Happy Holidays 🎁

---

Bug Fixes

• sync row defatil grid option to fix build (#1138) (f51220f) - by @ghiscoding

Features

• (re)add option to cancel Row Detail opening (#1136) (b4980ec) - by @ghiscoding

---

Installation

Please remember that all packages of @slickgrid-universal (v4.2.0) and Aurelia-Slickgrid (v7.2.1) must be updated at the same time and they will always get bumped on the same day to avoid any upgrade issues. You can also consult the Versions Compatibility Table - Wiki

please remember that Slickgrid-Universal monorepo now contains the biggest portion of the code (~90%), so most of the commits are now happening on that side.

1. review the Slickgrid-Universal changelog
2. and the Aurelia-Slickgrid changelog (above)

v7.1.0

7.1.0 (2023-12-21)

Quick Info

This new release fixes the demo with single locale (without using I18N), there are now 2 demos available in the external repo Aurelia-Slickgrid-Demos (with I18N and without I18N).

Bug Fixes

• I18N could be optional when providing single locale (#1129) (94fcfce) - by @ghiscoding

Features

• reimplement highlight row, node-extend & fix few issues (#1134) (c047781) - by @ghiscoding

---

Installation

Please remember that all packages of @slickgrid-universal (v4.1.0) and Aurelia-Slickgrid (v7.1.0) must be updated at the same time and they will always get bumped on the same day to avoid any upgrade issues. You can also consult the Versions Compatibility Table - Wiki

please remember that Slickgrid-Universal monorepo now contains the biggest portion of the code (~90%), so most of the commits are now happening on that side.

1. review the Slickgrid-Universal changelog
2. and the Aurelia-Slickgrid changelog (above)

v7.0.3 - Aurelia 2 (official release)

7.0.3 (2023-12-19)

Official Aurelia 2 Support

For real this time, starting with v7.0.3, Aurelia-Slickgrid is now working with Aurelia 2 🚀
A huge thanks to @MaximBalaganskiy he is the main player in getting this possible 👏🏻 🥇

⚠️ BREAKING CHANGES

• BREAKING CHANGE: migrate to Slickgrid-Universal v4.0 and Aurelia 2, fixes #709 (#1124) (8d0aa70), closes #709 #1124

Aurelia 2 is now required

Quick Info

The biggest change to this release is Aurelia 2 new minimum requirement

This new release is merging SlickGrid into the project and is dropping the previous external 6pac/slickgrid dependency. The aim of this release is to be standalone, improve best practices & move towards CSP compliance while also making the project leaner. Merging SlickGrid into the projects has a few benefits, the biggest are (easier to troubleshoot, drop unused code, deduplicate code like DOM utils, decrease external dependencies usage and finally a small decrease in build size).

Another great feature in conjunction with this release is a new Documentation website powered by GitBook. This should be more pleasing to read and also easier to receive documentation changes (note that because of the changes from Wiki to GitBook, some of the links might be invalid and if you find any then please submit a PR).

Read the Migration to 7.0 for all the changes

BREAKING CHANGES

• migrate to Slickgrid-Universal v4.0 and Aurelia 2, fixes #709

Bug Fixes

• spreading 2 grids options causes duplicate ext resources (#1126) (00a0be2)
• add missing types in pkg and fix cjs/esm exports (17eb5e8)

---

Installation

Please remember that all packages of @slickgrid-universal (v4.0.3) and Aurelia-Slickgrid (v7.0.3) must be updated at the same time and they will always get bumped on the same day to avoid any upgrade issues. You can also consult the Versions Compatibility Table - Wiki

please remember that Slickgrid-Universal monorepo now contains the biggest portion of the code (~90%), so most of the commits are now happening on that side.

1. review the Slickgrid-Universal changelog
2. and the Aurelia-Slickgrid changelog (above)

v7.0.2 - Aurelia 2 support

7.0.2 (2023-12-16)

Not Ready Yet

It looks like I went ahead a little too early on releasing this new version, the plugin build process is different in Aurelia 2 and I am still working on this part. Sorry for the delay