From 290335d2a957a0fc9737000ab8078f318d112739 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Wed, 10 May 2023 08:42:22 +0000 Subject: [PATCH] Apply automatic fixes --- rfc-216-use-static-typing-where-available.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rfc-216-use-static-typing-where-available.md b/rfc-216-use-static-typing-where-available.md index 17b81e5..929e627 100644 --- a/rfc-216-use-static-typing-where-available.md +++ b/rfc-216-use-static-typing-where-available.md @@ -39,8 +39,8 @@ code will be expected to handle. Where a language either includes support for static typing or where tooling exists to ensure it, new code we write SHOULD make use of static typing. -Where static typing is used in an interpreted language, any automated test pipeline MUST make sure that -types are checked. +Where static typing is used in an interpreted language, any automated test +pipeline MUST make sure that types are checked. If an existing project is in a language which supports optional or partial typing, you MAY choose to add type annotations to some, all or none of the