Skip to content

Delete wrong doc comment for Package.name #8843

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

Merged
merged 1 commit into from
Jun 21, 2025

Conversation

ole
Copy link
Contributor

@ole ole commented Jun 19, 2025

Deletes a sentence from the doc comments for Package.name that wrongly talks about the possibility of name being nil.

Motivation:

Package.name is a non-Optional property so it can never be nil, so the current documentation for it is factually wrong:

The name of the Swift package.

Discussion

If the name of the package is nil, Swift Package Manager deduces the name of the package using its Git URL.

Modifications:

  • Deleted part of a doc comment.

This deletes a sentence from the doc comments for `Package.name` that wrongly talks about the possibility of `name` being `nil`. `Package.name` is a non-Optional property so it can never be `nil`.
@plemarquand
Copy link
Contributor

@swift-ci please test

@plemarquand
Copy link
Contributor

@swift-ci test linux

@bkhouri bkhouri merged commit 29e5620 into swiftlang:main Jun 21, 2025
6 checks passed
marcprux pushed a commit to swift-everywhere/swift-package-manager that referenced this pull request Jul 7, 2025
Deletes a sentence from the doc comments for `Package.name` that wrongly
talks about the possibility of `name` being `nil`.

### Motivation:

`Package.name` is a non-Optional property so it can never be `nil`, so
[the current documentation for
it](https://developer.apple.com/documentation/packagedescription/package/name)
is factually wrong:

> The name of the Swift package.
>
> **Discussion**
>
> If the name of the package is `nil`, Swift Package Manager deduces the
name of the package using its Git URL.

### Modifications:

- Deleted part of a doc comment.
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