Skip to content

Instantly share code, notes, and snippets.

@DanielaSfregola
Last active August 8, 2017 19:48
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save DanielaSfregola/f5b31e03119a5d619ca391776b045fd5 to your computer and use it in GitHub Desktop.
Save DanielaSfregola/f5b31e03119a5d619ca391776b045fd5 to your computer and use it in GitHub Desktop.
Overall, quite easy -- but I had to read ALL the release notes quite carefully before doing anything else.
My approach is to usually bump the version and go through each compilation error and check the release
notes for instructions on how to fix them.
Key points where I struggled:
- I initially just bumped the version of found that it couldn't find the `cats` module anymore
- I had to ask for help on gitter cause it wasn't able to make `mapN` (substitute of `|@|`) compile
because of SI-2712 fix missing
- when reading the documentation, more of us thought that `mapN` actually meant `map2`, `map3`,
`map4`, etc...maybe an explicit before/after example could help?
There are fundamental steps of the migration process that should be highlighted probably more --
maybe in a well highlighted dedicated version?
(The cats module silly mistake was just me, but the missing SI-2712 was 3 of us!)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment