-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Part 1 of the PackageDescription DocC documentation update #4276
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
zkiraly
merged 18 commits into
swiftlang:main
from
zkiraly:zkiraly/documentation-update-1
Apr 23, 2022
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
59b63a5
Part 1 of the documentation update.
4262d29
Corrected the docs for two `Package.Dependency` methods.
81ccd41
Changed the docs for the C language standards in response to PR comme…
4c2f9ce
Updated all the language standard identifier docs.
b0a7cca
More responses to comments on the PR.
7421574
Responded to more comments.
b84390f
Merge branch 'main' into zkiraly/documentation-update-1
zkiraly 846916b
Some light editing of the DocC documentation.
405f3c1
More small edits.
32eddfd
More minor edits.
acc5ece
Merge branch 'main' into zkiraly/documentation-update-1
cd94221
Fixed a typo.
b6fc718
Removed unwanted blank-space.
105ba7f
Responding to Anders' notes.
44ba513
Merge branch 'apple:main' into zkiraly/documentation-update-1
zkiraly 5feb566
I should not have touched this file, so I am reverting my changes there.
f2958b9
We can't link below the top level for legal reasons.
2b50fb8
A small editorial change.
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion, it's easier to read if the documentation for each case is just "Swift 3", "Swift 4.2", etc. Most likely, a user reading it already knows that the symbols are identifiers for Swift language versions, so it's probably better to avoid information overload.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do need a sentence fragment ending in a period, as described in the API Design Guidelines under "Write a Documentation Comment." So I will leave this as is.