Make next major release: ps-0.12.x-v0.12.0

[JordanMartinez]

This is a bigger release with a number of breaking changes.

As of this release, we're now using Spago for our build tool and package manager, mainly because it eases the maintenance I would otherwise have to do.

Migrating

For things to work properly, there are 4 things you will need to do:

• install spago, dhall-to-json, and parcel via these installation instructions
• update the ide-purescript Atom package to the latest one to expose the additional spago option
• configure ide-purescript to build projects via spago by following the instructions listed in the second 'numbered list' here
• run the for-each-folder--install-deps-and-compile.sh, which will delete the old psc-package and pulp contents and build using spago

#303 needed to be added after this PR to account for the newer spago update.

Breaking Changes

• Fixes Rename 'Newtypes' file to 'Keyword--NewType' #264
• Fixes Relocate 'FP Philosophical Foundations' to a better location #255 - this was made into a top-level folder
• Fixes Delete 'why is learning fp so hard' file #254
• Fixes Move/Integrate 'Type Directed Search' into 'Typed Holes' file #252
• Fixes Remove 'Create Local Custom Package Set' file #251
• Fixes Add a Bower-based 'new project from start to finish' workflow page #250
• Fixes Split up 'Getting Started/ReadMe' into more files #249
• Fixes Split the 'Dependency Managers' file into separate files #248
• Fixes Finish explaining 'Why Learn Purescript' section #175
• Resolves Spacchetti-CLI is now Spago #194
• The pre-requisites / library overviews I do in the Projects folder were moved into their own folder called Libraries. These do not have a number ordering them as it allows me to add content in any order as I continue building new PS projects. Projects/Libraries/
• I broke the CLI Options mindmap up into separate SVG files, so that one can see all the CLI options for each program individually rather than a massive SVG file that tried to combine them into one image.
• Moved the explanation on type class dictionaries into Syntax folder that explains how they work: Syntax/Basic Syntax/Type Classes and Newtypes/Dictionaries: How Typeclasses Work.purs
• Cleaned up brief overview of monad transformers and Free: Hello World/Application Structure/ReadMe.md

New Content

• Fixes Add Domain Driven Design-related Design Patterns #288: linked to Scott's "Power of Composition" video in multiple places
  • Getting Started/Why Learn PS.md
  • FP Philosophical Foundations/Composition Everywhere.md
• In multiple places, linked to Nate's video on what problem type classes solve: code reuse:
  • Getting Started/Why Learn PS.md
  • FP Philosophical Foundations/Type Classes.md
• linked to Nate's video that explains what Free and Cofree are by using trees: Hello World/Application Structure/Free/ReadMe.md
• Fixes Link to community-curated list of companies using PS in production #295: Getting Started/Why Learn PS.md
• Fixes Link to Nate's talk on Free and CoFree #294: Hello World/Application Structure/Free/ReadMe.md
• Fixes Link to 'Introduction to Recusion Schemes' #293: Design Patterns/Recursion Schemes.md
• Fixes Link to 'TypeScript vs PureScript: not all compilers are created equal' #292: Getting Started/Why Learn PS.md
• Fixes Document that "super" type classes can use "sub" type classes' function in their implementation #253: Syntax/Basic Syntax/TypeClasses and Newtypes/Type Class Relationships.purs
• Addresses some parts of more on category theory - especially monad #147: "The Power of Composition" video explains monads in the correct way (composing two functions together that have 2 possible outputs). I also linked to the video in that issue, which highlights how we get the type signature for bind: the composition of two kleisli arrows.
• Documented a Spago workflow and how it works with parcel
• Added a visual that explains more of the laws behind Algebraic Data Types: FP Philosophical Foundations/Composition Everywhere.md
• Added a visual that explains the idea of immutable persistent data structures better: FP Philosophical Foundations/Data Types.md
• Added an overview of the control flow of some useful monads (Maybe, Either, List): Hello World/Prelude-ish/Control Flow/Useful Monads.md
• Linked to Traversable type classes' for function as a temporary explanation that helps one understand it better: Hello World/Prelude-ish/Foldable-Traversable/Traversable.md

Bugs Fixed

• The following bugs were fixed. It seems my TOC program's parser had a bug in it and I seemed to have missed it beforehand or had a specific structure that did not trigger the bug. I'm not too surprised by that because I didn't have any tests written for it since I was trying to push something out before refining it further. In the process, I also discovered a bug in purescript-tree (see bottom part of this PR for more context).

Other changes related to this project on a "meta" level:

• This repo sometimes used the folder names "images" and "resources" to refer to a folder that stored images or .graphml files to produce diagrams. I decided to rename all of those folders to assets instead and adhere to that naming convention.

[JordanMartinez]

Wow.... So, after many hours of trying to track down what's the bug that stops the ToC program from properly indenting the headers correctly, it seems there is a bug in purescript-tree:

module TreeBug where

import Prelude

import Control.Comonad.Cofree ((:<))
import Data.List (List(..), (:))
import Data.Maybe (maybe)
import Data.Tree (Tree, drawTree)
import Data.Tree.Zipper (down, fromTree, insertAfter, lastChild, next, toTree)
import Effect (Effect)
import Effect.Console (log)

-- Given a tree like so...
tree1 :: Tree String
tree1 =
  "a" :< ( ("b" :< Nil)
         : ("c" :< ( ("f" :< Nil)
                   : ("g" :< Nil)
                   : ("h" :< Nil)
                   : Nil ))
         : Nil
         )

main :: Effect Unit
main = do
  let loc = fromTree tree1

  -- 'f' and 'b' gets deleted when I use 'insertAfter'
  -- using 'lastChild' to get to that node
  log $ maybe "" (drawTree <<< toTree) do
    c <- lastChild loc
    f <- lastChild c

    let result = insertAfter ("z" :< Nil) f
    pure $ result

  log "========="

  -- 'f' and 'b' are not deleted when I use 'insertAfter'
  -- using a correct combination of 'down' and 'next' to get to the same node
  log $ maybe "" (drawTree <<< toTree) do
    b <- down loc
    c <- next b
    f <- down c

    let result = insertAfter ("z" :< Nil) f
    pure $ result

which outputs this:

a
|----> c
       |----> g
       |----> h
       |----> z

=========
a
|----> b
|----> c
       |----> f
       |----> z
       |----> g
       |----> h

Long story short, my parser was not correctly nesting markdown headers because I wasn't calling root at one part. I'm not sure whether this was something I missed earlier or something else. When I fixed it, I thought that solved the issue. Then, I learned that insertAfter doesn't work correctly. After more investigation, I saw that something was unexpectedly getting deleted and reproduced the following reproducible example when I investigated the tests of the library.

[JordanMartinez]

Ok. This release is ready. I just need to see whether CI passes or will also have issues.

[JordanMartinez]

The build passed but there's been some screwy things going on since it triggered 3 builds and cancelled 2 of them. So I guess GH didn't get the message or something.

[JordanMartinez]

The next tag has been pushed, but I'm not officially making a release yet. I need to update the PR's opening text to summarize all the changes I've done here as there are quite a lot.

I'll get to that on another day.

[JordanMartinez]

Ok. This PR's summary has been updated.