Now that v0.14. is out, we should fix any of the warnings found by the update in core libs. This issue tracks which of them need that and whether a PR has been submitted/merged yet. A checked box below means a PR has been submitted (but not necessarily merged). See methodology below for how this list was produced.
Method for producing the above list:
- Created a new project using
spago init
- Manually updated
packages.dhall file to update metadata.version = "v0.14.1"
- Ran
spago install $(spago ls packages | cut -f 1 -d ' ' | tr '\n' ' ') to install all packages in the set
- Ran
spago build --purs-args "--censor-codes='UserDefinedWarning'". I was trying to stop MonadZero deprecation notices from being include din list of warnings. I don't think this worked because censor-codes likely only works on source code defined in the src/ directory, not the .spago/ directory.
- Copied shell's output that listed all warnings into file called
fix-warnings-source
- Ran
cat fix-warnings-source | grep '.spago/' | cut -f 3 -d ' ' | cut -f 2 -d '/' | uniq > fix-warnings.txt (record a list of deduplicated packages that have a warning in them)
- Copied and pasted data into Excel file
- Ran
spago ls packages | grep '/purescript/' | cut -f 1 -d ' ' > purescript.txt to get a list of all core repos
- Ran
spago ls packages | grep '/purescript-contrib/' | cut -f 1 -d ' ' > purescript-contrib.txt to get a list of all contrib repos
- Pasted
purescript.txt and purescript-contib.txt into Excel fil
- Used
VLOOKUP Excel formula to find all purescript and purescript-contrib libs that had warnings.
This likely isn't the best method for determining things, but seems like it's likely 90% right.
Now that
v0.14.is out, we should fix any of the warnings found by the update in core libs. This issue tracks which of them need that and whether a PR has been submitted/merged yet. A checked box below means a PR has been submitted (but not necessarily merged). See methodology below for how this list was produced.Method for producing the above list:
spago initpackages.dhallfile to updatemetadata.version = "v0.14.1"spago install $(spago ls packages | cut -f 1 -d ' ' | tr '\n' ' ')to install all packages in the setspago build --purs-args "--censor-codes='UserDefinedWarning'". I was trying to stop MonadZero deprecation notices from being include din list of warnings. I don't think this worked becausecensor-codeslikely only works on source code defined in thesrc/directory, not the.spago/directory.fix-warnings-sourcecat fix-warnings-source | grep '.spago/' | cut -f 3 -d ' ' | cut -f 2 -d '/' | uniq > fix-warnings.txt(record a list of deduplicated packages that have a warning in them)spago ls packages | grep '/purescript/' | cut -f 1 -d ' ' > purescript.txtto get a list of all core reposspago ls packages | grep '/purescript-contrib/' | cut -f 1 -d ' ' > purescript-contrib.txtto get a list of all contrib repospurescript.txtandpurescript-contib.txtinto Excel filVLOOKUPExcel formula to find all purescript and purescript-contrib libs that had warnings.This likely isn't the best method for determining things, but seems like it's likely 90% right.