We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Attachment: Download
md5: c536abd6e1f81618ac79693f894f0da9
Issue Description:
Swift-DocC generally allows users to describe images with just the filename (ImageName), leaving out the file extension (.png).
For example, if a user included ImageName.png in their documentation catalog, they could refer to it with:
![Image description](ImageName)
However, when referencing images in Tutorials using the @image directive, DocC requires users to be explicit and use the file extension:
@Image(source: "ImageName.png", alt: "Image description")
This is confusing, so we should allow the following syntax:
@Image(source: "ImageName", alt: "Image description")
The text was updated successfully, but these errors were encountered:
Located the bug in Sources/SwiftDocC/Model/Rending/RenderNodeTranslator.swift line 1226
Sorry, something went wrong.
Pull Request link #3
Kyle-Ye
No branches or pull requests
Attachment: Download
Additional Detail from JIRA
md5: c536abd6e1f81618ac79693f894f0da9
Issue Description:
Swift-DocC generally allows users to describe images with just the filename (ImageName), leaving out the file extension (.png).
For example, if a user included ImageName.png in their documentation catalog, they could refer to it with:
![Image description](ImageName)
However, when referencing images in Tutorials using the @image directive, DocC requires users to be explicit and use the file extension:
@Image(source: "ImageName.png", alt: "Image description")
This is confusing, so we should allow the following syntax:
@Image(source: "ImageName", alt: "Image description")
The text was updated successfully, but these errors were encountered: