mirror of
https://github.com/dotnet/skills.git
synced 2026-09-20 09:49:54 +08:00
Dan Moseley
042a9d2b2c
* Reorganize plugins per agreed structure (#271) Split the dotnet plugin into domain-specific plugins per discussion in #271: - dotnet: narrowed to common everyday C#/.NET coding tasks - dotnet-diag: perf investigations, debugging, incident analysis - dotnet-data: data access and Entity Framework - dotnet-aspnet, dotnet-wpf, dotnet-winforms, dotnet-maui: scaffolded empty to convey intent for future framework-specific skills Moved skills, tests, and CODEOWNERS entries accordingly. No file content was changed; all skill/test moves are pure renames. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Improve dotnet-diag and dotnet-winforms descriptions - dotnet-diag: add '.NET' qualifier to clarify scope - dotnet-winforms: use official 'Windows Forms (WinForms)' name Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add .NET qualifier to dotnet-data description Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove empty plugins; list them in CONTRIBUTING.md as future options Remove the four empty placeholder plugins (dotnet-aspnet, dotnet-wpf, dotnet-winforms, dotnet-maui) that had only plugin.json and no skills. Add a 'Plugin organization' section to CONTRIBUTING.md that describes the domain-specific plugin groupings introduced in this PR and lists the four removed plugin names as reserved candidates for future contributions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Create dotnet-upgrade plugin with migration/upgrade skills Move migrate-nullable-references, thread-abort-migration, and dotnet-aot-compat from dotnet to the new dotnet-upgrade plugin. Update CODEOWNERS paths (same owners), CONTRIBUTING.md plugin table, and fix the thread-abort-migration SKILL.md link in CONTRIBUTING.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
40 lines
1.5 KiB
C#
40 lines
1.5 KiB
C#
// Copyright (c) Microsoft Corporation. All rights reserved.
|
|
// Licensed under the MIT License.
|
|
|
|
using System;
|
|
|
|
namespace Azure.Core
|
|
{
|
|
/// <summary>
|
|
/// Marks methods that call methods on other client and don't need their diagnostics verified.
|
|
/// </summary>
|
|
[AttributeUsage(AttributeTargets.Method, AllowMultiple = false, Inherited = true)]
|
|
internal class ForwardsClientCallsAttribute : Attribute
|
|
{
|
|
/// <summary>
|
|
/// Creates a new instance of <see cref="ForwardsClientCallsAttribute"/>.
|
|
/// </summary>
|
|
public ForwardsClientCallsAttribute()
|
|
: this(false)
|
|
{
|
|
}
|
|
|
|
/// <summary>
|
|
/// Creates a new instance of <see cref="ForwardsClientCallsAttribute"/>.
|
|
/// </summary>
|
|
/// <param name="skipChecks"> Sets whether or not diagnostic scope validation should happen. </param>
|
|
public ForwardsClientCallsAttribute(bool skipChecks)
|
|
{
|
|
SkipChecks = skipChecks;
|
|
}
|
|
|
|
/// <summary>
|
|
/// Gets whether or not we should validate DiagnosticScope for this API.
|
|
/// In the case where there is an internal API that makes the Azure API call and a public API that uses it we need ForwardsClientCalls.
|
|
/// If the public API will cache the results then the diagnostic scope will not always be created because an Azure API is not always called.
|
|
/// In this case we need to turn off this validation for this API only.
|
|
/// </summary>
|
|
public bool SkipChecks { get; }
|
|
}
|
|
}
|