linting

JasperFx · Oct 14, 2021 · cf90a45 · cf90a45
1 parent 0f1115c
commit cf90a45
Show file tree

Hide file tree

Showing 8 changed files with 5 additions and 15 deletions.
diff --git a/docs/diagnostics.md b/docs/diagnostics.md
@@ -364,7 +364,6 @@ theSession.Logger = new TestOutputMartenLogger(_output);
 <sup><a href='https://github.com/JasperFx/marten/blob/master/src/Marten.Testing/Events/archiving_events.cs#L230-L236' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_replacing_logger_per_session' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
-
 ## Previewing the PostgreSQL Query Plan
 
 Marten has a helper to find and preview the [PostgreSQL EXPLAIN plan](http://www.postgresql.org/docs/9.5/static/using-explain.html) for a Linq query. Our hope is that this will be a valuable aid to teams who need face performance problems while using Marten. The syntax for fetching the EXPLAIN plan for the Linq query from the previous section is shown below:

diff --git a/docs/documents/indexing/computed-indexes.md b/docs/documents/indexing/computed-indexes.md
@@ -84,7 +84,7 @@ var store = DocumentStore.For(_ =>
 
 The configuration above creates an index like this:
 
-```
+```sql
 CREATE INDEX mt_doc_user_idx_first_namelast_name ON public.mt_doc_user USING btree (((data ->> 'FirstName'::text)), ((data ->> 'LastName'::text)))
 ```
 

diff --git a/docs/documents/indexing/index.md b/docs/documents/indexing/index.md
@@ -18,4 +18,3 @@ My own personal bias is to avoid adding persistence concerns directly to the doc
 will prefer to use either attributes or the new embedded configuration option with the thinking that it's
 better to keep the persistence configuration on the document type itself for easier traceability. Either way,
 Marten has you covered with the various configuration options shown here.
-
diff --git a/docs/documents/querying/linq/strings.md b/docs/documents/querying/linq/strings.md
@@ -48,4 +48,3 @@ query.Query<User>().Single(x => x.UserName.EqualsIgnoreCase("aBc")).Id.ShouldBe(
 <!-- endSnippet -->
 
 This defaults to `String.Equals` with `StringComparison.CurrentCultureIgnoreCase` as comparison type.
-
diff --git a/docs/documents/querying/sql.md b/docs/documents/querying/sql.md
@@ -5,9 +5,7 @@ In all the code samples on this page, the `session` variable is of type
 `IQuerySession`.
 :::
 
-The Marten project strives to make the Linq provider robust and performant,
-but if there's ever a time when the Linq support is insufficient, you can 
-drop down to using raw SQL to query documents in Marten.
+The Marten project strives to make the Linq provider robust and performant, but if there's ever a time when the Linq support is insufficient, you can drop down to using raw SQL to query documents in Marten.
 
 Here's the simplest possible usage to query for `User` documents with a `WHERE` clause:
 

diff --git a/docs/documents/storing.md b/docs/documents/storing.md
@@ -38,9 +38,7 @@ await session.SaveChangesAsync();
 <sup><a href='https://github.com/JasperFx/marten/blob/master/src/Marten.Testing/Examples/StoringDocuments.cs#L37-L60' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_using_documentsession_store' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
-The `Store()` method can happily take a mixed bag of document types at one time, but you'll
-need to tell Marten to use `Store<object>()` instead of letting it infer the document type 
-as shown below:
+The `Store()` method can happily take a mixed bag of document types at one time, but you'll need to tell Marten to use `Store<object>()` instead of letting it infer the document type as shown below:
 
 <!-- snippet: sample_store_mixed_bag_of_document_types -->
 <a id='snippet-sample_store_mixed_bag_of_document_types'></a>
@@ -131,9 +129,7 @@ theSession.Query<Target>().Count().ShouldBe(data.Length);
 <sup><a href='https://github.com/JasperFx/marten/blob/master/src/Marten.Testing/CoreFunctionality/bulk_loading_async_Tests.cs#L94-L104' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_using_bulk_insert_async' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
-By default, bulk insert will fail if there are any duplicate id's between the documents being inserted and 
-the existing database data. You can alter this behavior through the `BulkInsertMode` enumeration
-as shown below:
+By default, bulk insert will fail if there are any duplicate id's between the documents being inserted and the existing database data. You can alter this behavior through the `BulkInsertMode` enumeration as shown below:
 
 <!-- snippet: sample_BulkInsertMode_usages -->
 <a id='snippet-sample_bulkinsertmode_usages'></a>

diff --git a/docs/events/archiving.md b/docs/events/archiving.md
@@ -49,4 +49,3 @@ var events = await theSession.Events.QueryAllRawEvents()
 ```
 <sup><a href='https://github.com/JasperFx/marten/blob/master/src/Marten.Testing/Events/archiving_events.cs#L196-L201' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_query_for_maybe_archived_events' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
-
diff --git a/docs/events/configuration.md b/docs/events/configuration.md
@@ -1,6 +1,6 @@
 # Event Store Configuration
 
-## Specifying the Schema 
+## Specifying the Schema
 
 The database schema name for the event store tables is by default, the same schema as the document store
 itself. The event storage can be explicitly moved to a separate schema as shown below: