From 88f0ab64c8d7956106a833100a9ac856e1ad8380 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakob=20Tikj=C3=B8b=20Andersen?= <jta@jakobandersen.com> Date: Thu, 16 Jan 2025 14:34:13 +0100 Subject: [PATCH] Correct FlatTableProjection being called FlatFileProjection --- docs/events/projections/flat.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/events/projections/flat.md b/docs/events/projections/flat.md index 76a92a815e..e9c9d134b3 100644 --- a/docs/events/projections/flat.md +++ b/docs/events/projections/flat.md @@ -161,9 +161,9 @@ public class FlatImportProjection: FlatTableProjection A couple notes on this version of the code: -* `FlatFileProjection` is adding columns to its table based on the designated column mappings. - You can happily customize the `FlatFileProjection.Table` object to add indexes, constraints, or defaults. -* Marten is able to apply schema migrations and manage the table from the `FlatFileProjection` as long as it’s registered with Marten. +* `FlatTableProjection` is adding columns to its table based on the designated column mappings. + You can happily customize the `FlatTableProjection.Table` object to add indexes, constraints, or defaults. +* Marten is able to apply schema migrations and manage the table from the `FlatTableProjection` as long as it’s registered with Marten. * When you call `Map(x => x.ActivityType)`, Marten is by default mapping that to a snake_cased derivation of the member name for the column, so “activity_type”. You can explicitly map the column name yourself. * The call to `Map(expression)` chains a fluent builder for the table column if you want to further customize the table