Fix MD linter warnings

duckdb · Sep 24, 2024 · be9ad67 · be9ad67
1 parent bc5f3f4
commit be9ad67
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 8 deletions.
diff --git a/_posts/2023-08-23-even-friendlier-sql.md b/_posts/2023-08-23-even-friendlier-sql.md
@@ -554,7 +554,6 @@ SELECT 'First Contact';
 <div class="narrow_table"></div>
 
 |       movie        |
-|     varchar        |
 |:---|
 | The Motion Picture |
 | First Contact      |
@@ -583,7 +582,6 @@ SELECT
 <div class="narrow_table"></div>
 
 |       movie        | type |        name        | num |
-| union(num integer, name varchar) | varchar |        varchar        | int32 |
 |:---|:---|:---|:---|
 | The Motion Picture | name | The Motion Picture |     |
 | 2                  | num  |                    | 2   |

diff --git a/docs/dev/release_calendar.md b/docs/dev/release_calendar.md
@@ -20,15 +20,15 @@ The planned dates of upcoming DuckDB releases are shown below.
 
 <div class="narrow_table"></div>
 
-<!-- markdownlint-disable MD055 MD056 -->
+<!-- markdownlint-disable MD055 MD056 MD058 -->
 
 | Date | Version |
 |:-----|--------:|
 {%- for release in site.data.upcoming_releases reversed %}
 | {{ release.start_date }} | {{ release.title | replace: "Release ", "" }} |
 {%- endfor %}
 
-<!-- markdownlint-enable MD055 MD056 -->
+<!-- markdownlint-enable MD055 MD056 MD058 -->
 
 ## Past Releases
 
@@ -38,17 +38,17 @@ In the following, we list DuckDB's past releases along with their codename where
 Between versions 0.2.2 and 0.3.3, all releases (including patch versions) received a codename.
 Since version 0.4.0, only major and minor versions get a codename.
 
-<!-- markdownlint-disable MD055 MD056 -->
+<!-- markdownlint-disable MD055 MD056 MD058 -->
 
 | Date | Version | Codename | Named after |      |
 |:-----|--------:|----------|-------------|------|
-{% for row in site.data.past_releases %}
+{%- for row in site.data.past_releases %}
     {%- capture logo_filename %}images/release-icons/{{ row.version_number }}.svg{% endcapture -%}
     {%- capture logo_exists %}{% file_exists {{ logo_filename }} %}{% endcapture -%}
     | {{ row.release_date }} | [{{ row.version_number }}](https://github.com/duckdb/duckdb/releases/tag/v{{ row.version_number }}) | {% if row.blog_post %}[{{ row.codename }}]({{ row.blog_post }}){% else %}{{ row.codename | default: "–" }}{% endif %} | {% if row.duck_wikipage %}<a href="{{ row.duck_wikipage }}">{% endif %}{{ row.duck_species_primary | default: "–" }}{% if row.duck_wikipage %}</a>{% endif %} {% if row.duck_species_secondary != nil %}_({{ row.duck_species_secondary }})_{% endif %} | {% if logo_exists == "true" %}![Logo of version {{ row.version_number }}](/{{ logo_filename }}){% endif %} |
-{% endfor %}
+{%- endfor %}
 
-<!-- markdownlint-enable MD055 MD056 -->
+<!-- markdownlint-enable MD055 MD056 MD058 -->
 
 You can get a [CSV file containing past DuckDB releases](/data/duckdb-releases.csv) and analyze it using DuckDB's [CSV reader]({% link docs/data/csv/overview.md %}).
 <!-- This also [works in the online DuckDB shell](https://shell.duckdb.org/#queries=v0,SELECT-release_date%2C-version_number%2C-codename%2C-duck_species_primary%2C-duck_species_secondary%0AFROM-'https%3A%2F%2Fduckdb.org%2Fdata%2Fduckdb%20releases.csv'~). -->