You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be a lot of overhead to just look through all inline code nodes and make them interlinks if they match? e.g.
This object inherits from `pydantic.BaseModel` and includes...
...use the `theme` argument of `shiny.express.ui.page_opts` to set the app theme.
A problem with the current interlinks syntax (besides the Sphinx syntax) is that most IDE hovercard implementations will treat quartodoc's interlink syntax as straight markdown, so unless you repeat the function name, e.g. [pydantic.BaseModel](`pydantic.BaseModel`), the text will be rendered with a blank spot where the empty link is.
In other words, if it's not prohibitive from a performance perspective, using regular inline code has the advantage of being a progressive enhancement. If quartodoc's interlinks filters are present they can be promoted to links; otherwise in all other situations the text renders as desired just without the link.
Based on discussion in #315, it would be nice to allow a interlinks short-hand, to shorten links like
[](`target`)
.The main reason for this is that the longform is useful for customizing display name (e.g.
[some name](`target`)
), but cumbersome otherwise.It seems like two important factors are:
`:target`
as a shorthand, then it will become hard to represent the literal code block:target
.The text was updated successfully, but these errors were encountered: