This message, related to the development of the theme, only displays on the localhost homepage to notify you of any important theme changes.

Version 2.0.0 - July 20, 2020

Below are the following changes that could be breaking changes for your site. For more details on any change, please refer to PR #154.

The major breaking change is:

  1. Users that have front matter that utilize images (backwards compatibility for featured and associated parameters still remains) will need to adjust from [images]="SRC" to the new format.
[[images]]
    src = "" // Link to image
    alt = "" // Alt text for image
    stretch = // Optional: See screenshots for referenced values and outcomes

If you utilize any of the following, there might be a breaking:

  1. User custom templates may require adjustment.
  2. User custom i18n languages, or custom templates referencing i18n translations may require adjustment.
  3. User custom template for comments will require adjustment if it uses the theme’s CSS and/or JS.
  4. User custom CSS may need to adjust due to a variety of class name changes and specificity changes.

While I realize this is inconvenient, I hope that it is worth it to you in the long run. Thanks for using the theme, and feel free to submit issues as needed.

rendle.dev

Mark Rendle's .NET development blog.

Nullable References in Enumerables

Handling nullable reference types in IEnumerable operations

2-Minute Read

I’m a big fan of the Nullable Reference Types feature added in C# 8.0. It lets the compiler catch a bunch of potential runtime errors, and I guarantee if you turn it on you’ll get a bunch of warnings. As of .NET 5.0, the entire BCL is now covered with nullable annotations, and a lot of the extended ecosystem supports them too.

Creating a dotnet tool

Building, packaging and publishing a `dotnet` tool via NuGet

9-Minute Read

One of the great features of .NET Core is that it gives you a simple way to create and distribute CLI tools via NuGet. You just create a Console application, add a few entries to the .csproj file, and publish it to NuGet. Then other people can install it with the dotnet tool install command. I’ve published a couple of tools this way before, but I’ve just published another one so I thought I’d take time to describe the steps involved, as well as a handful of neat NuGet packages…

Recent Posts

Categories

About

Mark Rendle's blog about making software and stuff.