rambda 10.0.0-beta.1 → 10.0.0

package/CHANGELOG.md

@@ -81,14 +81,20 @@ This is major revamp of `Rambda` library:
 -- R.rejectObject
 -- R.findNth
 -- R.combinations
--- R.rangeDescending
+-- R.sortByPath
+-- R.sortByPathDescending
+-- R.sortByDescending
+-- R.flattenObject
+-- R.addPropToObjects
 
 - Rename following methods:
 
--- replaceItemAtIndex -> adjust
+-- modifyItemAtIndex -> adjust
 -- checkObjectWithSpec -> where 
 -- objectIncludes -> whereEq
 -- modify -> modifyProp
+-- chain -> flatMap
+-- mapObjIndexed -> mapObject
 
 _ Regarding using object as input with TypeScript in methods such as `R.map/filter` - this feature is no longer supported in TypeScript as it has multiple issues when using inside pipes. In JS, it still works as before. Following methods are affected:
 
@@ -116,7 +122,9 @@ _ Regarding using object as input with TypeScript in methods such as `R.map/filt
 
 -- append/prepend
 
-- Change `R.range` to work with `endIndex` included instead of `endIndex` excluded, i.e. `R.range(0, 2)` will return `[0, 1, 2]` instead of `[0, 1]`. This is done because `R.rangeDescending` is added and users would wonder if end or start index is excluded.
+- Change `R.range` to work with descending order.
+
+- Remove `rambda/immutable` as import option as it is hard to support in the new context.
 
 - Sync with typing of `@types/ramda`:
 
@@ -169,11 +177,6 @@ _ Regarding using object as input with TypeScript in methods such as `R.map/filt
 
 - Revert adding stopper logic in `R.reduce` - https://github.com/selfrefactor/rambda/pull/630
 
-- Renamed methods: 
-
--- `chain` to `flatMap`
--- `mapObjIndexed` to `mapObject`
-
 9.4.2
 
 - Fix TS issue when `R.take` is used as part of `R.pipe`.