-
Notifications
You must be signed in to change notification settings - Fork 128
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
Structure suggestions for link resolution warnings as fixits #438
Labels
enhancement
Improvements or enhancements to existing functionality
Comments
d-ronnqvist
added
the
enhancement
Improvements or enhancements to existing functionality
label
Dec 13, 2022
3 tasks
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Jan 6, 2023
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Jan 6, 2023
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Jan 6, 2023
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Jan 6, 2023
3 tasks
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Jan 6, 2023
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Jan 18, 2023
2 tasks
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Jan 29, 2023
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Feb 8, 2023
theMomax
added a commit
to theMomax/swift-docc
that referenced
this issue
Feb 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a documentation link fails to resolve, the diagnostic doesn't have any structured suggestions (fixits).
With the hierarchy-based link resolver implementation there's information about how to change the link so that it would resolve but this information is included in the error message text.
If we moved this information into
Solution
elements with aReplacement
then IDEs could display them as fixits so that the developer could easily apply one of them.Note that the link resolver doesn't have all the information it needs to create the
Solution
/Replacement
elements (e.g. the source range or URL).The text was updated successfully, but these errors were encountered: