yv01p/Umbraco-CMS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Removes notes

Browse Source
This commit is contained in:
Shannon
2019-02-20 20:37:10 +11:00
parent 91c52cffc8
commit 717efb6b09
3 changed files with 1 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/Umbraco.Core/Services/Implement/PackagingService.cs
View File

@@ -3,26 +3,14 @@ using System.Collections.Generic;
using System.IO;
using System.Linq;
using System.Net.Http;
using System.Text.RegularExpressions;
using System.Threading.Tasks;
using System.Web;
using System.Xml.Linq;
using Semver;
using Umbraco.Core.Collections;
using Umbraco.Core.Events;
using Umbraco.Core.Exceptions;
using Umbraco.Core.IO;
using Umbraco.Core.Logging;
using Umbraco.Core.Models;
using Umbraco.Core.Models.Entities;
using Umbraco.Core.Models.Packaging;
using Umbraco.Core.Packaging;
using Umbraco.Core.Persistence.Querying;
using Umbraco.Core.Persistence.Repositories;
using Umbraco.Core.PropertyEditors;
using Umbraco.Core.Scoping;
using Umbraco.Core.Strings;
using Content = Umbraco.Core.Models.Content;
namespace Umbraco.Core.Services.Implement
{

9
src/Umbraco.Web/Mvc/PluginController.cs
View File

@@ -22,14 +22,7 @@ namespace Umbraco.Web.Mvc
// for debugging purposes
internal Guid InstanceId { get; } = Guid.NewGuid();
// note
// properties marked as [Inject] below will be property-injected (vs constructor-injected) in
// order to keep the constructor as light as possible, so that ppl implementing eg a SurfaceController
// don't need to implement complex constructors + need to refactor them each time we change ours.
// this means that these properties have a setter.
// what can go wrong?
/// <summary>
/// Gets the Umbraco context.
/// </summary>

6
src/Umbraco.Web/Mvc/UmbracoViewPageOfTModel.cs
View File

@@ -26,12 +26,6 @@ namespace Umbraco.Web.Mvc
private UmbracoContext _umbracoContext;
private UmbracoHelper _helper;
// note
// properties marked as [Inject] below will be property-injected (vs constructor-injected) since
// we have no control over the view constructor (generated by eg the Razor engine).
// this means that these properties have a setter.
// what can go wrong?
/// <summary>
/// Gets or sets the database context.
/// </summary>