Skip to content

Clarify that SdkAnalysisLevel impacts more than just this warning #3447

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

nkolev92
Copy link
Member

Progress on NuGet/Home#14369.

The idea is that we'd be adding this disclaimer to every place we recommend SDKAnalysisLevel.

My plan is to update https://github.com/NuGet/NuGet.Client/blob/dev/docs/feature-guide.md#warnings-and-defaults once the wording here has been approved.

@Copilot Copilot AI review requested due to automatic review settings July 18, 2025 20:50
@nkolev92 nkolev92 requested review from a team as code owners July 18, 2025 20:50
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a documentation note to clarify that changing SDKAnalysisLevel affects more than just the NU1302 warning being discussed. The change adds a reference note directing users to the official SDK documentation for comprehensive information about all features impacted by SDKAnalysisLevel.

  • Adds a note section with disclaimer about SDKAnalysisLevel side effects
  • References the official .NET SDK documentation for complete feature scope
Comments suppressed due to low confidence (1)

docs/reference/errors-and-warnings/NU1302.md:55

  • The property name casing is inconsistent. The text uses 'SDKAnalysisLevel' but the link references 'SdkAnalysisLevel'. Both should use the same casing for consistency.
> Changing SDKAnalysisLevel has other side-effects as well. Refer to the [`SdkAnalysisLevel`](/dotnet/core/project-sdk/msbuild-props#sdkanalysislevel) for a summary of the full scope of .NET SDK features affected.

@nkolev92 nkolev92 requested review from baronfel and zivkan July 18, 2025 20:50
Copy link

Learn Build status updates of commit 3f97e7c:

✅ Validation status: passed

File Status Preview URL Details
docs/reference/errors-and-warnings/NU1302.md ✅Succeeded View

For more details, please refer to the build report.

@nkolev92 nkolev92 requested a review from Nigusu-Allehu July 18, 2025 20:51
Copy link

Learn Build status updates of commit 1b0bba6:

✅ Validation status: passed

File Status Preview URL Details
docs/reference/errors-and-warnings/NU1302.md ✅Succeeded View

For more details, please refer to the build report.

@nkolev92 nkolev92 changed the title Clarify that SDKAnalysisLevel impacts more than just this warning Clarify that SdkAnalysisLevel impacts more than just this warning Jul 18, 2025
@@ -51,4 +51,5 @@ Here's how it functions:
- For SDK Analysis Level value **below 9.0.100**, using HTTP sources triggers a warning ([NU1803](NU1803.md)).
- Starting with SDK Analysis Level **9.0.100 or higher**, HTTP sources result in an error (NU1302) unless `AllowInsecureConnections` is explicitly enabled.


> [!NOTE]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we consider a different alert, perhaps warning, caution, or important?

https://learn.microsoft.com/en-us/contribute/content/markdown-reference#alerts-note-tip-important-caution-warning

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are maybe, at least an Important, but possibly a warning. I feel like Caution is potentially too much.

@baronfel what do you think about this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy