Skip to content

Commit cfac184

Browse files
ghiscodingghiscoding
committed
docs: update migration guides
1 parent 0e439dc commit cfac184

5 files changed

Lines changed: 15 additions & 15 deletions

File tree

‎docs/migrations/migration-to-10.x.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,9 +47,9 @@ _following changes should be transparent to most users_
4747

4848
### Selection Models, keeping only `SlickHybridSelectionModel`
4949

50-
1. rename `rowSelectionOptions` to `selectionOptions`
51-
2. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
52-
3. drop both `enableHybridSelection`/`enableRowSelection` merge them into a new `enableSelection` grid option
50+
1. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
51+
2. drop both `enableHybridSelection`/`enableRowSelection` and merge them into a new `enableSelection` grid option
52+
3. rename `rowSelectionOptions` grid option to `selectionOptions`
5353

5454
`SlickHybridSelectionModel` was previously introduced in order to merge and allow using both Cell/Row Selections separately and/or in combo on the same grid. It was introduced in v9.x to test it out and after testing it for a few months, it's now safe to drop the older `SlickCellSelectionModel` / `SlickRowSelectionModel` models and keep only the hybrid model (for smaller build & less code to maintain). Also, since we now have the Hybrid model and it's now accepting options for different selection models, I think it's better to rename `rowSelectionOptions` to `selectionOptions` since it now makes more sense with the hybrid approach and you will need to update your code when using Row Selection, see below:
5555

‎frameworks/angular-slickgrid/docs/migrations/migration-to-10.x.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,9 +72,9 @@ _following changes should be transparent to most users_
7272

7373
### Selection Models, keeping only `SlickHybridSelectionModel`
7474

75-
1. rename `rowSelectionOptions` to `selectionOptions`
76-
2. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
77-
3. drop both `enableHybridSelection`/`enableRowSelection` merge them into a new `enableSelection` grid option
75+
1. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
76+
2. drop both `enableHybridSelection`/`enableRowSelection` and merge them into a new `enableSelection` grid option
77+
3. rename `rowSelectionOptions` grid option to `selectionOptions`
7878

7979
`SlickHybridSelectionModel` was previously introduced in order to merge and allow using both Cell/Row Selections separately and/or in combo on the same grid. It was introduced in v9.x to test it out and after testing it for a few months, it's now safe to drop the older `SlickCellSelectionModel` / `SlickRowSelectionModel` models and keep only the hybrid model (for smaller build & less code to maintain). Also, since we now have the Hybrid model and it's now accepting options for different selection models, I think it's better to rename `rowSelectionOptions` to `selectionOptions` since it now makes more sense with the hybrid approach and you will need to update your code when using Row Selection, see below:
8080

‎frameworks/aurelia-slickgrid/docs/migrations/migration-to-10.x.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,9 @@ _following changes should be transparent to most users_
6868

6969
### Selection Models, keeping only `SlickHybridSelectionModel`
7070

71-
1. rename `rowSelectionOptions` to `selectionOptions`
72-
2. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
73-
3. drop both `enableHybridSelection`/`enableRowSelection` merge them into a new `enableSelection` grid option
71+
1. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
72+
2. drop both `enableHybridSelection`/`enableRowSelection` and merge them into a new `enableSelection` grid option
73+
3. rename `rowSelectionOptions` grid option to `selectionOptions`
7474

7575
`SlickHybridSelectionModel` was previously introduced in order to merge and allow using both Cell/Row Selections separately and/or in combo on the same grid. It was introduced in v9.x to test it out and after testing it for a few months, it's now safe to drop the older `SlickCellSelectionModel` / `SlickRowSelectionModel` models and keep only the hybrid model (for smaller build & less code to maintain). Also, since we now have the Hybrid model and it's now accepting options for different selection models, I think it's better to rename `rowSelectionOptions` to `selectionOptions` since it now makes more sense with the hybrid approach and you will need to update your code when using Row Selection, see below:
7676

‎frameworks/slickgrid-react/docs/migrations/migration-to-10.x.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,9 @@ _following changes should be transparent to most users_
6868

6969
### Selection Models, keeping only `SlickHybridSelectionModel`
7070

71-
1. rename `rowSelectionOptions` to `selectionOptions`
72-
2. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
73-
3. drop both `enableHybridSelection`/`enableRowSelection` merge them into a new `enableSelection` grid option
71+
1. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
72+
2. drop both `enableHybridSelection`/`enableRowSelection` and merge them into a new `enableSelection` grid option
73+
3. rename `rowSelectionOptions` grid option to `selectionOptions`
7474

7575
`SlickHybridSelectionModel` was previously introduced in order to merge and allow using both Cell/Row Selections separately and/or in combo on the same grid. It was introduced in v9.x to test it out and after testing it for a few months, it's now safe to drop the older `SlickCellSelectionModel` / `SlickRowSelectionModel` models and keep only the hybrid model (for smaller build & less code to maintain). Also, since we now have the Hybrid model and it's now accepting options for different selection models, I think it's better to rename `rowSelectionOptions` to `selectionOptions` since it now makes more sense with the hybrid approach and you will need to update your code when using Row Selection, see below:
7676

‎frameworks/slickgrid-vue/docs/migrations/migration-to-10.x.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -82,9 +82,9 @@ _following changes should be transparent to most users_
8282

8383
### Selection Models, keeping only `SlickHybridSelectionModel`
8484

85-
1. rename `rowSelectionOptions` to `selectionOptions`
86-
2. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
87-
3. drop both `enableHybridSelection`/`enableRowSelection` merge them into a new `enableSelection` grid option
85+
1. drop both `SlickCellSelectionModel`/`SlickRowSelectionModel` and keep only `SlickHybridSelectionModel`
86+
2. drop both `enableHybridSelection`/`enableRowSelection` and merge them into a new `enableSelection` grid option
87+
3. rename `rowSelectionOptions` grid option to `selectionOptions`
8888

8989
`SlickHybridSelectionModel` was previously introduced in order to merge and allow using both Cell/Row Selections separately and/or in combo on the same grid. It was introduced in v9.x to test it out and after testing it for a few months, it's now safe to drop the older `SlickCellSelectionModel` / `SlickRowSelectionModel` models and keep only the hybrid model (for smaller build & less code to maintain). Also, since we now have the Hybrid model and it's now accepting options for different selection models, I think it's better to rename `rowSelectionOptions` to `selectionOptions` since it now makes more sense with the hybrid approach and you will need to update your code when using Row Selection, see below:
9090

0 commit comments

Comments
 (0)