Bump the testing group across 2 directories with 3 updates

[dependabot]

Bumps the testing group with 2 updates in the /example/Fornax.Seo.Example directory: fantomas-tool and fsdocs-tool.
Bumps the testing group with 3 updates in the /test/Fornax.Seo.Tests directory: fantomas-tool, fsdocs-tool and NUnit.

Updates fantomas-tool from 4.4.0 to 4.7.9

Changelog

Sourced from fantomas-tool's changelog.

[4.7.9] - 2022-05-02

Changed

• Add fable_modules to the directories which are always excluded. Fable 3.4

Fixed

• Let binding after match lambda is moved outside of nested module. #2214

[4.7.8] - 2022-04-25

Fixed

• Breaks float range with step-size when trailing 0 is omitted. #2171
• Fantomas inserts a space between array variable and indexer. #2106

[4.7.7] - 2022-04-20

Fixed

• Multiline parentheses objectExpression in indexer expression. #2176
• Blank line over SynEnumCase is restored incorrectly. #2155
• XML Doc comments on DU cases seem to get shuffled. #2188
• Comment after bar is lost in single case DU. #2182
• Piped lambda with if-then-else can break code. #2196

[4.7.6] - 2022-04-04

Fixed

• SRTP or condition disappear when non-generic type is used. #2168
• Multiline AbstractSlot without constraints introduces newline #2175

[4.7.5] - 2022-03-27

Fixed

• Only load the .fantomasignore file once, except for the daemon. #2097

[4.7.4] - 2022-03-25

Fixed

• DotGet in quotation should be further indented. #2154
• Reformatting multiple array index operators (v6 style) adds spaces that are invalid #2151

[4.7.3] - 2022-03-12

Fixed

• Option parameter name is lost in tuple. #2144
• Trivia between XmlDoc and member is not printed. #2147
• Emit correct keyword for properties with both getter and setter specified #2129
• Duplicate ///-comments when immediately preceded by a //-comment. #2152

[4.7.2] - 2022-03-11

... (truncated)

Commits

• See full diff in compare view

Updates fsdocs-tool from 19.1.1 to 20.0.1

Changelog

Sourced from fsdocs-tool's changelog.

20.0.1 - 2024-05-31

• Details improvements. #917

20.0.0 - 2024-02-14

Stable release

20.0.0-beta-002 - 2024-02-08

Fixed

• Avoid theme flicker in dark mode. #901

20.0.0-beta-001 - 2024-01-31

Changed

• Marking development of v20 as complete.

20.0.0-alpha-019 - 2024-01-29

Fixed

• Use dvh for full viewport height . #899

20.0.0-alpha-018 - 2024-01-10

Fixed

• Add -webkit-text-size-adjust. #889

20.0.0-alpha-017 - 2024-01-09

Fixed

• Set default font-size for code. #889

20.0.0-alpha-016 - 2023-12-07

Fixed

• Use empty replacement for {{fsdocs-meta-tags} in API doc pages. #892

20.0.0-alpha-015 - 2023-12-06

Fixed

• Namespace description overflows content box. #886

Added

• SEO-optimization for new theme. Allow description and keywords in frontmatter. Introduce {{fsdocs-meta-tags}}. #869

20.0.0-alpha-014 - 2023-11-22

Added

• Added the ability to use ipynb files as inputs #874

... (truncated)

Upgrade guide

Sourced from fsdocs-tool's upgrade guide.

---

category: Advanced categoryindex: 3 index: 1

Upgrading to fsdocs

Here are the typical steps to upgrade a repo based on ProjectScaffold to use fsdocs

1. Run

   [lang=text]
   dotnet new tool
   dotnet tool install fsdocs-tool
   

2. Delete all of docs\tools particularly docs\tool\generate.fsx. Keep a copy of any templates for reference as you'll have to copy some bits across to the new template.

3. Put your docs directory so it reflects the final shape of the site. For example move the content of docs\input\* and docs\files\* directly to docs\*

4. Follow the notes in styling to start to style your site.

5. Run

   [lang=text]
   dotnet fsdocs watch
   

   and edit and test your docs.

6. If using FAKE adjust build.fsx e.g.

   [lang=text]
   Target.create "GenerateDocs" (fun _ ->
      Shell.cleanDir ".fsdocs"
      DotNet.exec id "fsdocs" "build --clean" |> ignore
   )
   Target.create "ReleaseDocs" (fun _ ->
   Git.Repository.clone "" projectRepo "temp/gh-pages"
   Git.Branches.checkoutBranch "temp/gh-pages" "gh-pages"
   Shell.copyRecursive "output" "temp/gh-pages" true |> printfn "%A"
   Git.CommandHelper.runSimpleGitCommand "temp/gh-pages" "add ." |> printfn "%s"
   let cmd = sprintf """commit -a -m "Update generated documentation for version %s""" release.NugetVersion
   Git.CommandHelper.runSimpleGitCommand "temp/gh-pages" cmd |> printfn "%s"
   Git.Branches.push "temp/gh-pages"
   )
   

7. Consider creating docs\_template.fsx and docs\_template.ipynb to enable co-generation of F# scripts and F# notebooks.

   If you add support for notebooks and scripts, consider adding mybinder links to each of your literate executable content pages. For example like this.

... (truncated)

Commits

• See full diff in compare view

Updates fantomas-tool from 4.4.0 to 4.7.9

Changelog

Sourced from fantomas-tool's changelog.

[4.7.9] - 2022-05-02

Changed

• Add fable_modules to the directories which are always excluded. Fable 3.4

Fixed

• Let binding after match lambda is moved outside of nested module. #2214

[4.7.8] - 2022-04-25

Fixed

• Breaks float range with step-size when trailing 0 is omitted. #2171
• Fantomas inserts a space between array variable and indexer. #2106

[4.7.7] - 2022-04-20

Fixed

• Multiline parentheses objectExpression in indexer expression. #2176
• Blank line over SynEnumCase is restored incorrectly. #2155
• XML Doc comments on DU cases seem to get shuffled. #2188
• Comment after bar is lost in single case DU. #2182
• Piped lambda with if-then-else can break code. #2196

[4.7.6] - 2022-04-04

Fixed

• SRTP or condition disappear when non-generic type is used. #2168
• Multiline AbstractSlot without constraints introduces newline #2175

[4.7.5] - 2022-03-27

Fixed

• Only load the .fantomasignore file once, except for the daemon. #2097

[4.7.4] - 2022-03-25

Fixed

• DotGet in quotation should be further indented. #2154
• Reformatting multiple array index operators (v6 style) adds spaces that are invalid #2151

[4.7.3] - 2022-03-12

Fixed

• Option parameter name is lost in tuple. #2144
• Trivia between XmlDoc and member is not printed. #2147
• Emit correct keyword for properties with both getter and setter specified #2129
• Duplicate ///-comments when immediately preceded by a //-comment. #2152

[4.7.2] - 2022-03-11

... (truncated)

Commits

• See full diff in compare view

Updates fsdocs-tool from 19.1.1 to 20.0.1

Changelog

Sourced from fsdocs-tool's changelog.

20.0.1 - 2024-05-31

• Details improvements. #917

20.0.0 - 2024-02-14

Stable release

20.0.0-beta-002 - 2024-02-08

Fixed

• Avoid theme flicker in dark mode. #901

20.0.0-beta-001 - 2024-01-31

Changed

• Marking development of v20 as complete.

20.0.0-alpha-019 - 2024-01-29

Fixed

• Use dvh for full viewport height . #899

20.0.0-alpha-018 - 2024-01-10

Fixed

• Add -webkit-text-size-adjust. #889

20.0.0-alpha-017 - 2024-01-09

Fixed

• Set default font-size for code. #889

20.0.0-alpha-016 - 2023-12-07

Fixed

• Use empty replacement for {{fsdocs-meta-tags} in API doc pages. #892

20.0.0-alpha-015 - 2023-12-06

Fixed

• Namespace description overflows content box. #886

Added

• SEO-optimization for new theme. Allow description and keywords in frontmatter. Introduce {{fsdocs-meta-tags}}. #869

20.0.0-alpha-014 - 2023-11-22

Added

• Added the ability to use ipynb files as inputs #874

... (truncated)

Upgrade guide

Sourced from fsdocs-tool's upgrade guide.

---

category: Advanced categoryindex: 3 index: 1

Upgrading to fsdocs

Here are the typical steps to upgrade a repo based on ProjectScaffold to use fsdocs

1. Run

   [lang=text]
   dotnet new tool
   dotnet tool install fsdocs-tool
   

2. Delete all of docs\tools particularly docs\tool\generate.fsx. Keep a copy of any templates for reference as you'll have to copy some bits across to the new template.

3. Put your docs directory so it reflects the final shape of the site. For example move the content of docs\input\* and docs\files\* directly to docs\*

4. Follow the notes in styling to start to style your site.

5. Run

   [lang=text]
   dotnet fsdocs watch
   

   and edit and test your docs.

6. If using FAKE adjust build.fsx e.g.

   [lang=text]
   Target.create "GenerateDocs" (fun _ ->
      Shell.cleanDir ".fsdocs"
      DotNet.exec id "fsdocs" "build --clean" |> ignore
   )
   Target.create "ReleaseDocs" (fun _ ->
   Git.Repository.clone "" projectRepo "temp/gh-pages"
   Git.Branches.checkoutBranch "temp/gh-pages" "gh-pages"
   Shell.copyRecursive "output" "temp/gh-pages" true |> printfn "%A"
   Git.CommandHelper.runSimpleGitCommand "temp/gh-pages" "add ." |> printfn "%s"
   let cmd = sprintf """commit -a -m "Update generated documentation for version %s""" release.NugetVersion
   Git.CommandHelper.runSimpleGitCommand "temp/gh-pages" cmd |> printfn "%s"
   Git.Branches.push "temp/gh-pages"
   )
   

7. Consider creating docs\_template.fsx and docs\_template.ipynb to enable co-generation of F# scripts and F# notebooks.

   If you add support for notebooks and scripts, consider adding mybinder links to each of your literate executable content pages. For example like this.

... (truncated)

Commits

• See full diff in compare view

Updates NUnit from 4.2.2 to 4.3.0

Release notes

Sourced from NUnit's releases.

NUnit 4.3.0

See release notes

Commits

• e50c99b prepare 4.3.0 (#4895)
• f46c6d8 Merge pull request #4883 from nunit/AsyncSingleThread
• 18f9331 Always specify context parameter to AsyncToSyncAdapter.Await
• 5a4f35c Async Test continuations now also run on the same thread when SIngleThreaded ...
• f597da8 Merge pull request #4891 from nunit/Issue4887
• 6831f66 Merge pull request #4882 from manfred-brands/typeSpecificEqualConstraints
• 0c1ef7f Add a .NET 8.0 target (#4884)
• cddb8a9 Fix for issue #4887
• 6e14a0f Merge pull request #4888 from Saurav-shres/use-first-instead-of-toarray
• 90502f1 Refactor TestAssert: Replace ToArray()[0] with First() for efficiency.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.