Fixing all the TODO, FIXME & HACK comments so they all follow the same layout.

This commit is contained in:
Chris Houston
2019-01-27 01:17:32 -05:00
committed by Sebastiaan Janssen
parent d31e25281d
commit 193e24afd2
338 changed files with 573 additions and 586 deletions

View File

@@ -36,7 +36,7 @@ namespace Umbraco.Web.PublishedCache.NuCache.DataSource
// write each variation
foreach (var (culture, variation) in variations)
{
// todo - it's weird we're dealing with cultures here, and languageId in properties
// TODO: it's weird we're dealing with cultures here, and languageId in properties
PrimitiveSerializer.String.WriteTo(culture, stream); // should never be null
WriteObject(variation.Name, stream); // write an object in case it's null (though... should not happen)

View File

@@ -15,7 +15,7 @@ using static Umbraco.Core.Persistence.NPocoSqlExtensions.Statics;
namespace Umbraco.Web.PublishedCache.NuCache.DataSource
{
// todo - use SqlTemplate for these queries else it's going to be horribly slow!
// TODO: use SqlTemplate for these queries else it's going to be horribly slow!
// provides efficient database access for NuCache
internal class DatabaseDataSource : IDataSource

View File

@@ -12,14 +12,14 @@ namespace Umbraco.Web.PublishedCache.NuCache.DataSource
public string Culture
{
get => _culture;
set => _culture = value ?? throw new ArgumentNullException(nameof(value)); // todo or fallback to string.Empty? CANNOT be null
set => _culture = value ?? throw new ArgumentNullException(nameof(value)); // TODO: or fallback to string.Empty? CANNOT be null
}
[JsonProperty("seg")]
public string Segment
{
get => _segment;
set => _segment = value ?? throw new ArgumentNullException(nameof(value)); // todo or fallback to string.Empty? CANNOT be null
set => _segment = value ?? throw new ArgumentNullException(nameof(value)); // TODO: or fallback to string.Empty? CANNOT be null
}
[JsonProperty("val")]