swift
organizes new articles into the existing pages for descriptions and groups
#82350
Closed

organizes new articles into the existing pages for descriptions and groups #82350

heckj wants to merge 1 commit into main from diagnostics-curation
heckj
heckj55 days ago (edited 55 days ago)

Updates the curation (organization) for the newer articles in diagnostics.

3 articles were floating below the organized pages - this merges them into those groups.

  • 1 new diagnostic description
  • 2 new group descriptions

Reviewed manually with:

cd userdocs
xcrun docc preview diagnostics --allow-arbitrary-catalog-directories
heckj heckj requested a review from bnbarham bnbarham 55 days ago
heckj heckj assigned heckj heckj 55 days ago
heckj
heckj55 days ago

@swift-ci please test

bnbarham
bnbarham commented on 2025-06-18
Conversation is marked as resolved
Show resolved
userdocs/diagnostics/diagnostic-groups.md
3234- <doc:strict-memory-safety>
3335- <doc:unknown-warning-group>
34
36- <doc:availability-unrecognized-name>
37
- <doc:missing-module-on-known-paths>
bnbarham55 days ago (edited 55 days ago)šŸ‘ 1

Ah... I really need to add that check I said I'd add in 😬 Thanks for adding these. I know you didn't add it, but would you like to summarize the initial paragraph in missing-module-on-known-paths? It's a bit long for the one-liner IMO.

EDIT: Also, mind making the additions alphabetical?

heckj53 days ago

I don't have a sense for the size this will grow to, but if the list gets notably longer, it would make a lot of sense to start looking for ways to group these rather than utilizing alphabetical organization. And even that's tricky, as not all the markdown file names align to the titles in those articles. Changing the markdown file name will change the the URL that the page is pinned out, so if you're referencing these externally - I'd recommend being quite strict about those changes, and maybe building up a convention of always naming the markdown file after the name of the Group or Diagnostic.

I'd be happy to retrofit the markdown file name in a separate PR if you'd like to go that route.

bnbarham50 days ago (edited 50 days ago)

I'm not sure there really is another great way to group these (outside of the existing grouping I added).

and maybe building up a convention of always naming the markdown file after the name of the Group or Diagnostic

I can add a check for this when I add one for the docs themselves. @DougGregor / @hborla any opinions here? Seems reasonable to expect the title + filename to match. Now is probably the best time to fix that up if we do want it.

tshortli50 days agošŸ‘ 1

I don't have a sense for the size this will grow to, but if the list gets notably longer, it would make a lot of sense to start looking for ways to group these rather than utilizing alphabetical organization.

As an eventual upper bound, every single warning diagnostic (and probably some error diagnostics) could have its own group (though practically speaking, many groups will cover more than one diagnostic). I just grepped main and count 372 warnings (and 10 times as many errors).

Conversation is marked as resolved
Show resolved
userdocs/diagnostics/diagnostic-descriptions.md
3535- <doc:string-interpolation-conformance>
3636- <doc:temporary-pointers>
3737- <doc:trailing-closure-matching>
38
- <doc:implementation-only-deprecated>
bnbarham55 days ago (edited 55 days ago)

This is a diagnostic group isn't it (CC @artemcm)?

EDIT: Yep -

include/swift/AST/DiagnosticGroups.def
52:GROUP(ImplementationOnlyDeprecated, "implementation-only-deprecated")
bnbarham55 days agošŸ‘ 1

Whoops, this was meant to be a @tshortli ping (Artem was one of the ones below)

heckj
heckj53 days ago

@swift-ci please test

heckj organizes new articles into the existing pages for descriptions and g…
98b0e7b5
heckj heckj force pushed from 9f694051 to 98b0e7b5 34 days ago
heckj heckj closed this 34 days ago
heckj heckj deleted the diagnostics-curation branch 34 days ago

Login to write a write a comment.

Login via GitHub

Reviewers
Assignees
Labels
Milestone