Skip to content

Commit e755435

Browse files
committed
Rename the update-cache-key-on-publish setting to be update-cache-on-publish
Now that the key doens't actually change!
1 parent 21d7f92 commit e755435

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Our.Umbraco.TagHelpers/UmbracoCacheTagHelper.cs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ public class UmbracoCacheTagHelper : CacheTagHelper
2222
/// <summary>
2323
/// Whether to update the cache key when any content, media, dictionary item is published in Umbraco.
2424
/// </summary>
25-
public bool UpdateCacheKeyOnPublish { get; set; } = true;
25+
public bool UpdateCacheOnPublish { get; set; } = true;
2626

2727
public UmbracoCacheTagHelper(CacheTagHelperMemoryCacheFactory factory,
2828
HtmlEncoder htmlEncoder,
@@ -53,8 +53,8 @@ public override async Task ProcessAsync(TagHelperContext context, TagHelperOutpu
5353
// we want to do the same by default for this tag helper
5454
// we can't track by convention as dot net tag helper cache key is hashed - but we can generte the hash key here, and add it to a dictionary
5555
// which we can loop through when the Umbraco cache is updated to clear the tag helper cache.
56-
// you can opt out of this by setting update-cache-key-on-publish="false" in the individual tag helper
57-
if (UpdateCacheKeyOnPublish)
56+
// you can opt out of this by setting update-cache-on-publish="false" in the individual tag helper
57+
if (UpdateCacheOnPublish)
5858
{
5959
// The base TagHelper would generate it's own CacheTagKey to create a unique hash
6060
// but if we call it here 'too' it will fortunately be the same hash.

0 commit comments

Comments
 (0)