Julien Gonzalez

I think we should let people chose their own third-party library to process Unicode strings properly. I don't see much value in supporting strings as "containers of characters" in Ramda....

It is possible I haven't fully grasped the specifics of this proposal but as far as I can tell we could do something similar with `pathEq`: ```javascript pathEq([2], 'math', ['apple',...

I somehow missed that release :/ Not sure what happened here as `v0.28.1` doesn't exist either. There are ongoing discussions about typings perhaps it was done for that purpose (I...

> the `ramda-ts-self` name should only be on the `ts` branch. If I've changed it somewhere else that messes with the master branch/normal release process please revert! The package name...

Hi all. Sorry for the radio silence lately. I started a new job and have busy weeks at the moment. Fortunately that commit sits before two major breaking changes so...

> will `merge` still work after the update? Nope. As per the release notes `merge` has been removed completely in `0.28`. You can use either `mergeLeft` or `mergeRight` instead

# Replacing `composeP` with `composeWith` Based from https://github.com/ramda/ramda/issues/3099 Before: ```javascript import * as R from 'ramda'; import { promises as fs } from 'fs'; await R.composeP( JSON.parse, R.toString, fs.readFile, )('path/to/file');...

@sudo-cho Indeed we've missed that but it has since been fixed in #3254. Just need to rebuild and redeploy the documentation.

@CrossEye Shall we close this for now?

@CrossEye I'm tempted to reopen as we have docs and test cases. Perhaps we can simply drop the type signature for now?