[flow][docs] Add  markers to stub blog posts

gkz · meta-codesync[bot] · commit 9f058fa5bf80 · 2026-05-19T13:53:50.000-07:00
Summary:
Building the website printed a Docusaurus warning listing 46 blog posts without truncation markers. Each affected post is a short stub that points at a Medium article via `medium-link` in its frontmatter — there is no full-article body on the Flow site, so the rendered post is essentially equal to the preview.

To silence the warning while preserving the current presentation, append `&lt;!--truncate--&gt;` at the end of each affected post. This matches the marker style already used in the rest of `website/blog/` (e.g. `2015-02-20-Flow-Comments.md`) and tells Docusaurus that the entire stub body is the preview, which is what gets rendered on the blog index today anyway.

Changelog: [internal]

Reviewed By: marcoww6

Differential Revision: D105734945

fbshipit-source-id: ec902c17c01b3254fdfdd40f78ae27a1ee3081fe
diff --git a/website/blog/2015-07-29-Version-0.14.0.md b/website/blog/2015-07-29-Version-0.14.0.md
@@ -10,3 +10,5 @@ This post announced Flow v0.14.0. For current features and behavior, see the [Fl
 It has come to our attention that not everyone obsessively checks GitHub for Flow releases. This came as a surprise, but we would like to support these users too. Therefore, we will start announcing each Flow release on the blog, starting with this release.
 
 So here is Flow v0.14.0! Check out the [Changelog](https://github.com/facebook/flow/blob/master/Changelog.md#v0140) for the canonical list of what has changed.
+
+<!--truncate-->
diff --git a/website/blog/2015-09-10-Version-0.15.0.md b/website/blog/2015-09-10-Version-0.15.0.md
@@ -10,3 +10,5 @@ This post announced Flow v0.15.0. For current features and behavior, see the [Fl
 Today we released Flow v0.15.0! A lot has changed in the last month and we're excited to get the hard work of all our contributors in front of people! Big thanks to everyone who contributed to this release!
 
 Check out the [Changelog](https://github.com/facebook/flow/blob/master/Changelog.md#v0150) to see what's new.
+
+<!--truncate-->
diff --git a/website/blog/2015-09-22-Version-0.16.0.md b/website/blog/2015-09-22-Version-0.16.0.md
@@ -10,3 +10,5 @@ This post announced Flow v0.16.0. For current features and behavior, see the [Fl
 On Friday we released Flow v0.16.0! We had some major perf improvements that we wanted to get into a release, plus let/const support was ready (thanks again [@samwgoldman](https://github.com/samwgoldman))!
 
 As always, the [Changelog](https://github.com/facebook/flow/blob/master/Changelog.md#v0160) is best at summing up the big changes.
+
+<!--truncate-->
diff --git a/website/blog/2015-10-07-Version-0.17.0.md b/website/blog/2015-10-07-Version-0.17.0.md
@@ -12,3 +12,5 @@ Today we released Flow v0.17.0! The first thing you may notice is that we change
 This should hopefully help our command line users understand many errors without having to refer to their source code. We'll keep iterating on this format, so tell us what you like and what you don't like! Thanks to [@frantic](https://github.com/frantic) for building this feature!
 
 There are a whole bunch of other features and fixes in this release! Head on over to our [Release](https://github.com/facebook/flow/releases/tag/v0.17.0) for the full list!
+
+<!--truncate-->
diff --git a/website/blog/2017-07-27-Opaque-Types.md b/website/blog/2017-07-27-Opaque-Types.md
@@ -11,3 +11,5 @@ This post announced opaque type aliases when it was introduced. For current synt
 
 Do you ever wish that you could hide your implementation details away
 from your users? Find out how opaque type aliases can get the job done!
+
+<!--truncate-->
diff --git a/website/blog/2017-08-04-Linting-in-Flow.md b/website/blog/2017-08-04-Linting-in-Flow.md
@@ -10,3 +10,5 @@ This post announced Flow's linter when it was introduced. For current syntax and
 :::
 
 Flow’s type information is useful for so much more than just proving your programs are correct. Introducing Flow linter.
+
+<!--truncate-->
diff --git a/website/blog/2017-08-16-Even-Better-Support-for-React-in-Flow.md b/website/blog/2017-08-16-Even-Better-Support-for-React-in-Flow.md
@@ -12,3 +12,5 @@ This post announced React support in Flow when it was introduced. For current sy
 The first version of Flow support for React was a magical implementation of
 `React.createClass()`. Since then, React has evolved significantly. It is time
 to rethink how Flow models React.
+
+<!--truncate-->
diff --git a/website/blog/2017-08-25-Private-Object-Properties-Using-Flows-Opaque-Type-Aliases.md b/website/blog/2017-08-25-Private-Object-Properties-Using-Flows-Opaque-Type-Aliases.md
@@ -15,3 +15,5 @@ from users of your classes. However, locking yourself in to an OOP style of
 programming is not always ideal if you prefer a more functional style. Let’s
 talk about how you can use Flow’s [opaque type aliases](https://flow.org/en/docs/types/opaque-types/) to get private properties
  on any object type.
+
+<!--truncate-->
diff --git a/website/blog/2017-09-03-Flow-Support-in-Recompose.md b/website/blog/2017-09-03-Flow-Support-in-Recompose.md
@@ -13,3 +13,5 @@ One month ago [Recompose](https://github.com/acdlite/recompose) landed an
 official Flow library definition. The definitions were a long time coming,
 considering the original PR was created by
 [@GiulioCanti](https://twitter.com/GiulioCanti) a year ago.
+
+<!--truncate-->
diff --git a/website/blog/2018-02-20-Better-Flow-Error-Messages-for-the-Javascript-Ecosystem.md b/website/blog/2018-02-20-Better-Flow-Error-Messages-for-the-Javascript-Ecosystem.md
@@ -13,3 +13,5 @@ Over the last year, the Flow team has been slowly auditing and improving all the
 possible error messages generated by the type checker. In Flow 0.66 we’re
 excited to announce a new error message format designed to decrease the time it
 takes you to read and fix each bug Flow finds.
+
+<!--truncate-->
diff --git a/website/blog/2018-03-16-New-Flow-Errors-on-Unknown-Property-Access-in-Conditionals.md b/website/blog/2018-03-16-New-Flow-Errors-on-Unknown-Property-Access-in-Conditionals.md
@@ -11,3 +11,5 @@ This post announced errors on unknown property access in conditionals when it wa
 
 TL;DR: Starting in 0.68.0, Flow will now error when you access unknown
 properties in conditionals.
+
+<!--truncate-->
diff --git a/website/blog/2018-10-18-Exact-Objects-By-Default.md b/website/blog/2018-10-18-Exact-Objects-By-Default.md
@@ -10,3 +10,5 @@ This post described exact objects by default at the time of writing. For current
 :::
 
 We are changing object types to be exact by default. We'll be releasing codemods to help you upgrade.
+
+<!--truncate-->
diff --git a/website/blog/2018-10-29-Asking-for-Required-Annotations.md b/website/blog/2018-10-29-Asking-for-Required-Annotations.md
@@ -11,3 +11,5 @@ This post announced required annotations when it was introduced. For current syn
 
 Flow will be asking for more annotations starting in 0.85.0. Learn how
 to deal with these errors in our latest blog post.
+
+<!--truncate-->
diff --git a/website/blog/2018-12-13-React-Abstract-Component.md b/website/blog/2018-12-13-React-Abstract-Component.md
@@ -11,3 +11,5 @@ This post announced React.AbstractComponent when it was introduced. For current
 
 We made some major changes to our React model to better model new React components. Let's
 talk about React.AbstractComponent!
+
+<!--truncate-->
diff --git a/website/blog/2019-08-20-Changes-to-Object-Spreads.md b/website/blog/2019-08-20-Changes-to-Object-Spreads.md
@@ -10,3 +10,5 @@ This post announced changes to object spreads when it was introduced. For curren
 :::
 
 Changes are coming to how Flow models object spreads! Learn more in this post.
+
+<!--truncate-->
diff --git a/website/blog/2019-1-28-What-the-flow-team-has-been-up-to.md b/website/blog/2019-1-28-What-the-flow-team-has-been-up-to.md
@@ -10,3 +10,5 @@ This post described the Flow team's work in 2018 at the time of writing and may
 :::
 
 Take a look at what the Flow was up to in 2018.
+
+<!--truncate-->
diff --git a/website/blog/2019-10-25-Live-Flow-Errors-in-your-IDE.md b/website/blog/2019-10-25-Live-Flow-Errors-in-your-IDE.md
@@ -10,3 +10,5 @@ This post announced live Flow errors in IDEs when it was introduced. For current
 :::
 
 Live errors while you type makes Flow feel faster in your IDE!
+
+<!--truncate-->
diff --git a/website/blog/2019-10-30-Spreads-Common-Errors-and-Fixes.md b/website/blog/2019-10-30-Spreads-Common-Errors-and-Fixes.md
@@ -10,3 +10,5 @@ This post described object spread errors at the time of writing. For current syn
 :::
 
 Fixes to object spreads will expose errors in your codebase. Read more about common errors and how to fix them.
+
+<!--truncate-->
diff --git a/website/blog/2019-2-8-A-More-Responsive-Flow.md b/website/blog/2019-2-8-A-More-Responsive-Flow.md
@@ -10,3 +10,5 @@ This post announced Flow performance improvements when it was introduced. Syntax
 :::
 
 Flow 0.92 improves on the Flow developer experience.
+
+<!--truncate-->
diff --git a/website/blog/2019-4-9-Upgrading-Flow-Codebases.md b/website/blog/2019-4-9-Upgrading-Flow-Codebases.md
@@ -10,3 +10,5 @@ This post described upgrading Flow codebases at the time of writing. The migrati
 :::
 
 Having trouble upgrading from 0.84.0? Read about how the Flow team upgrades Flow at Facebook!
+
+<!--truncate-->
diff --git a/website/blog/2020-01-29-How-to-Upgrade-to-exact-by-default-object-type-syntax.md b/website/blog/2020-01-29-How-to-Upgrade-to-exact-by-default-object-type-syntax.md
@@ -10,3 +10,5 @@ This post described upgrading to exact-by-default object type syntax at the time
 :::
 
 Object types will become exact-by-default. Read this post to learn how to get your code ready!
+
+<!--truncate-->
diff --git a/website/blog/2020-02-19-Improvements-to-Flow-in-2019.md b/website/blog/2020-02-19-Improvements-to-Flow-in-2019.md
@@ -10,3 +10,5 @@ This post described improvements to Flow in 2019 at the time of writing and may
 :::
 
 Take a look back at improvements we made to Flow in 2019.
+
+<!--truncate-->
diff --git a/website/blog/2020-03-09-What-were-building-in-2020.md b/website/blog/2020-03-09-What-were-building-in-2020.md
@@ -10,3 +10,5 @@ This post described the Flow team's plans for 2020 at the time of writing and ma
 :::
 
 Learn about how Flow will improve in 2020. 
+
+<!--truncate-->
diff --git a/website/blog/2020-03-16-Making-Flow-error-suppressions-more-specific.md b/website/blog/2020-03-16-Making-Flow-error-suppressions-more-specific.md
@@ -10,3 +10,5 @@ This post announced more specific error suppressions when it was introduced. For
 :::
 
 We’re improving Flow error suppressions so that they don’t accidentally hide errors.
+
+<!--truncate-->
diff --git a/website/blog/2020-05-18-Types-First-A-Scalable-New-Architecture-for-Flow.md b/website/blog/2020-05-18-Types-First-A-Scalable-New-Architecture-for-Flow.md
@@ -10,3 +10,5 @@ This post announced the Types-First architecture when it was introduced. Syntax
 :::
 
 Flow Types-First mode is out! It unlocks Flow’s potential at scale by leveraging fully typed module boundaries. Read more in our latest blog post.
+
+<!--truncate-->
diff --git a/website/blog/2020-11-16-Flows-Improved-Handling-of-Generic-Types.md b/website/blog/2020-11-16-Flows-Improved-Handling-of-Generic-Types.md
@@ -10,3 +10,5 @@ This post announced improved handling of generic types when it was introduced. F
 :::
 
 Flow has improved its handling of generic types by banning unsafe behaviors previously allowed and clarifying error messages.
+
+<!--truncate-->
diff --git a/website/blog/2020-12-01-Types-first-the-only-supported-mode-in-flow.md b/website/blog/2020-12-01-Types-first-the-only-supported-mode-in-flow.md
@@ -10,3 +10,5 @@ This post announced Types-First becoming the only supported mode when it was int
 :::
 
 Types-First will become the only mode in Flow in v0.143 (mid Jan 2021).
+
+<!--truncate-->
diff --git a/website/blog/2021-05-25-Clarity-on-Flows-Direction-and-Open-Source-Engagement.md b/website/blog/2021-05-25-Clarity-on-Flows-Direction-and-Open-Source-Engagement.md
@@ -10,3 +10,5 @@ This post described Flow's direction and open source engagement at the time of w
 :::
 
 An update on Flow's direction and open source engagement.
+
+<!--truncate-->
diff --git a/website/blog/2021-06-02-Sound-Typing-for-this-in-Flow.md b/website/blog/2021-06-02-Sound-Typing-for-this-in-Flow.md
@@ -10,3 +10,5 @@ This post announced sound typing for `this` when it was introduced. For current
 :::
 
 Improvements in soundness for `this`-typing in Flow, including the ability to annotate `this` on functions and methods.
+
+<!--truncate-->
diff --git a/website/blog/2021-07-21-Introducing-Flow-Indexed-Access-Types.md b/website/blog/2021-07-21-Introducing-Flow-Indexed-Access-Types.md
@@ -10,3 +10,5 @@ This post announced indexed access types when it was introduced. For current syn
 :::
 
 Flow’s Indexed Access Types are a new type annotation syntax that allows you to get the type of a property from an object, array, or tuple type.
+
+<!--truncate-->
diff --git a/website/blog/2021-09-13-Introducing-Flow-Enums.md b/website/blog/2021-09-13-Introducing-Flow-Enums.md
@@ -10,3 +10,5 @@ This post announced Flow Enums when it was introduced. For current syntax and be
 :::
 
 Flow Enums are an opt-in feature which allow you to define a fixed set of constants which create their own type.
+
+<!--truncate-->
diff --git a/website/blog/2021-09-13-TypeScript-Enums-vs-Flow-Enums.md b/website/blog/2021-09-13-TypeScript-Enums-vs-Flow-Enums.md
@@ -10,3 +10,5 @@ This post announced TypeScript Enums vs. Flow Enums when it was introduced. For
 :::
 
 A comparison of the enums features of TypeScript and Flow.
+
+<!--truncate-->
diff --git a/website/blog/2021-09-27-Introducing-Local-Type-Inference-for-Flow.md b/website/blog/2021-09-27-Introducing-Local-Type-Inference-for-Flow.md
@@ -10,3 +10,5 @@ This post announced local type inference when it was introduced. For current syn
 :::
 
 We're replacing Flow’s current inference engine with a system that behaves more predictably and can be reasoned about more locally.
+
+<!--truncate-->
diff --git a/website/blog/2022-08-05-New-Flow-Language-Rule-Constrained-Writes.md b/website/blog/2022-08-05-New-Flow-Language-Rule-Constrained-Writes.md
@@ -10,3 +10,5 @@ This post announced the constrained writes rule when it was introduced. For curr
 :::
 
 Flow is releasing a new language rule that determines the type of an unannotated variable at its initialization. Along with these new rules come several fixes to soundness bugs that were causing refinements to not be invalidated.
+
+<!--truncate-->
diff --git a/website/blog/2022-09-30-Requiring-More-Annotations-on-Functions-and-Classes.md b/website/blog/2022-09-30-Requiring-More-Annotations-on-Functions-and-Classes.md
@@ -10,3 +10,5 @@ This post announced increased annotation requirements for functions and classes
 :::
 
 Flow will now require more annotations to functions and classes.
+
+<!--truncate-->
diff --git a/website/blog/2022-10-20-Improved-handling-of-the-empty-object-in-Flow.md b/website/blog/2022-10-20-Improved-handling-of-the-empty-object-in-Flow.md
@@ -10,3 +10,5 @@ This post announced improved handling of the empty object when it was introduced
 :::
 
 Flow handled the empty object literal {} in a permissive but unsafe way. The fix described in this post increases safety and predictability, but requires using different patterns and behavior.
+
+<!--truncate-->
diff --git a/website/blog/2023-01-17-Local-Type-Inference.md b/website/blog/2023-01-17-Local-Type-Inference.md
@@ -10,3 +10,5 @@ This post announced local type inference when it was introduced. For current syn
 :::
 
 Local Type Inference makes Flow’s inference behavior more reliable and predictable, by modestly increasing Flow’s annotation requirement, bringing it closer to industry standard and capitalizing on increasingly strongly and explicitly typed codebases.
+
+<!--truncate-->
diff --git a/website/blog/2023-02-16-Exact-object-types-by-default-by-default.md b/website/blog/2023-02-16-Exact-object-types-by-default-by-default.md
@@ -10,3 +10,5 @@ This post announced exact object types becoming the default when it was introduc
 :::
 
 We announced 5 years ago a plan to eventually make exact object types the default. We are now proceeding with this plan.
+
+<!--truncate-->
diff --git a/website/blog/2023-03-15-Announcing-Partial-and-Required-Flow-utility-types-and-catch-annotations.md b/website/blog/2023-03-15-Announcing-Partial-and-Required-Flow-utility-types-and-catch-annotations.md
@@ -11,3 +11,5 @@ This post announced Partial, Required, and catch annotations when it was introdu
 
 Starting in Flow version 0.201, make an object type’s fields all optional using `Partial<ObjType>` (use instead of the unsafe `$Shape`),
 and make an object type’s optional fields required with `Required<ObjType>`.
+
+<!--truncate-->
diff --git a/website/blog/2023-04-10-Unused-Promise.md b/website/blog/2023-04-10-Unused-Promise.md
@@ -12,3 +12,5 @@ This post announced unused Promise detection when it was introduced. For current
 As of v0.201.0, Flow can now lint against unused/floating Promises. Unused promises can be dangerous,
 because errors are potentially unhandled, and the code may not execute in the intended order. They are
 usually mistakes that Flow is perfectly positioned to warn you about.
+
+<!--truncate-->
diff --git a/website/blog/2023-08-17-Announcing-5-new-Flow-tuple-type-features.md b/website/blog/2023-08-17-Announcing-5-new-Flow-tuple-type-features.md
@@ -10,3 +10,5 @@ This post announced new tuple type features when it was introduced. For current
 :::
 
 Labeled tuple elements, read-only tuples, optional tuple elements, tuple spread, and more.
+
+<!--truncate-->
diff --git a/website/blog/2023-09-19-Improved-Flow-Docs-and-Try-Flow.md b/website/blog/2023-09-19-Improved-Flow-Docs-and-Try-Flow.md
@@ -5,3 +5,5 @@ authors: [george-zahariev]
 medium-link: "https://medium.com/flow-type/improved-flow-docs-and-try-flow-5da5e4831b5e"
 ---
 We’ve refreshed our documentation, and added the ability to configure options and lints in Try Flow!
+
+<!--truncate-->
diff --git a/website/blog/2024-02-06-New-type-casting-syntax-for-Flow-as.md b/website/blog/2024-02-06-New-type-casting-syntax-for-Flow-as.md
@@ -10,3 +10,5 @@ This post announced the `as` type casting syntax when it was introduced. For cur
 :::
 
 To make it easier for new users to get started with Flow, we’re updating our type casting syntax to use 'as'.
+
+<!--truncate-->
diff --git a/website/blog/2024-03-05-Announcing-Conditional-Types.md b/website/blog/2024-03-05-Announcing-Conditional-Types.md
@@ -10,3 +10,5 @@ This post announced conditional types when it was introduced. For current syntax
 :::
 
 Conditional types allow you to choose between two different output types by inspecting an input type.
+
+<!--truncate-->
diff --git a/website/blog/2024-03-05-Announcing-User-Defined-Type-Guards-in-Flow.md b/website/blog/2024-03-05-Announcing-User-Defined-Type-Guards-in-Flow.md
@@ -10,3 +10,5 @@ This post announced user-defined type guards when it was introduced. For current
 :::
 
 Flow now lets you define a function that encodes a type predicate over its parameter.
+
+<!--truncate-->
diff --git a/website/blog/2024-04-03-New-Flow-Language-Features-for-React.md b/website/blog/2024-04-03-New-Flow-Language-Features-for-React.md
@@ -10,3 +10,5 @@ This post announced component and hook syntax for React when it was introduced.
 :::
 
 Flow is excited to announce Component Syntax, adding first-class support for React primitives such as components and hooks to the Flow language. These features bring improved ergonomics, expressiveness, and static enforcement for many of the Rules of React.
+
+<!--truncate-->
