Skip to content
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

Clarify what a package being available means #3360

Merged
merged 5 commits into from
Nov 19, 2024

Conversation

nkolev92
Copy link
Member

See motivation: NuGet/Home#13930 (comment).

tldr; If a package content resource lists a package as available, it should be able to download.
Being unavailable breaks the contract.

@nkolev92 nkolev92 requested review from a team as code owners November 18, 2024 23:36
Copy link

Learn Build status updates of commit b2ef23c:

✅ Validation status: passed

File Status Preview URL Details
docs/api/package-base-address-resource.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit 74e44e2:

✅ Validation status: passed

File Status Preview URL Details
docs/api/package-base-address-resource.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@nkolev92 nkolev92 requested a review from donnie-msft November 18, 2024 23:47
Copy link

Learn Build status updates of commit 1303f7c:

✅ Validation status: passed

File Status Preview URL Details
docs/api/package-base-address-resource.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

Comment on lines 39 to 42
If the client knows a package ID and wants to discover which package versions the package source has available, the
client can construct a predictable URL to enumerate all package versions. This list is meant to be a "directory
client can construct a predictable URL to enumerate all package versions. Every version listed in this list must be available for download.
This list is meant to be a "directory
listing" for the package content API mentioned below.
Copy link
Member

Choose a reason for hiding this comment

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

I suggest reformatting this to one complete sentence per line.

@nkolev92 nkolev92 force-pushed the dev-nkolev92-contentIMprovements branch from 1303f7c to 95ca569 Compare November 19, 2024 17:38
Copy link

Learn Build status updates of commit 95ca569:

✅ Validation status: passed

File Status Preview URL Details
docs/api/package-base-address-resource.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit ec06f03:

✅ Validation status: passed

File Status Preview URL Details
docs/api/package-base-address-resource.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@nkolev92 nkolev92 merged commit 09a979d into main Nov 19, 2024
2 checks passed
@nkolev92 nkolev92 deleted the dev-nkolev92-contentIMprovements branch November 19, 2024 17:50
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.

6 participants