Test formatting (#19)

* Format MediaQueriesSpec tests.

* Format AnimationsSpec tests.

* Format SelectorsSpec tests.

* Format AlignSpec tests.

* Format BackgroundSpec tests.

* Format BoxSpec tests.

* Format ColorSpec tests.

* Format ContentSpec tests.

* Format DisplaySpec tests.

* Format FlexboxSpec tests.

* Format FontsSpec tests.

* Format GridSpec tests.

* Format ImagesSpec tests.

* Format InlineSpec tests.

* Format ListsSpec tests.

* Format Test.Main.

* Format MaskingSpec tests.

* Format OverflowSpec tests.

* Format PositionSpec tests.

* Format RenderSpec tests.

* Format SizingSpec tests.

* Format TextDecorSpec tests.

* Format TextSpec tests.

* Format TransformsSpec tests.

* Format TransitionsSpec tests.

* Format UISpec tests.

* Format test utils.

* Format VisufxSpec tests.

* Format VisurenSpec tests.

* Format WritingModesSpec tests.

* Updates around formatting.

* Formatting changelog entry

Author: nsaunders

.github/workflows/ci.yml

@@ -41,7 +41,7 @@ jobs:
         run: spago -x test.dhall test
 
       - name: Check formatting
-        run: purs-tidy check src
+        run: purs-tidy check examples src test
 
       - name: Install Node.js dependencies
         run: npm install

CHANGELOG.md

@@ -13,7 +13,7 @@ New features:
 Bugfixes:
 
 Other improvements:
-- Examples are now formatted using `purs-tidy`.
+- Examples and tests are now formatted using `purs-tidy`.
 
 ## [0.1.5] - 2022-12-05
 New features:

CONTRIBUTING.md

@@ -40,9 +40,7 @@ The `src` directory includes the following modules:
 
 Usually your work will begin in the `Tecton.Internal` module. From this module, export the minimum functions, types, and classes required for client code to compile. Then, from the `Tecton` module, re-export only the subset that client code should interact with directly. This architecture clearly defines the public API while allowing implementation details to remain flexible.
 
-After making any changes, run `purs-tidy format-in-place examples src` to format the code.
-
-> ⚠️ **NOTE**: For now, only format the modules in the `examples` and `src` directories. Formatting for tests is under review.
+After making any changes, run `purs-tidy format-in-place examples src test` to format the code.
 
 Unit test(s) should accompany each change. Ensure that the system under test (e.g. the new property binding you added) is imported from the `Tecton` module so that tests accurately represent client code. Tests are organized into modules corresponding to W3C CSS specifications, which can be found [here](https://www.w3.org/TR/css-2021/), and almost always follow this format: