> In terms of UX, if someone already has a searchfox permalink with revision, it seems like it would be less work for them to just use that link directly? Yeah, I think I agree here. You'd have to permalink and then cut the revision out. I wouldn't mind WONTFIXing this if a `/lastrev/` endpoint is unlikely to happen anytime soon. > so my personal recommendation to people would be to use markdown for docs since firefox-source-docs can render markdown too Note that because we use [myst](https://myst-parser.readthedocs.io/en/latest/syntax/roles-and-directives.html#roles-an-in-line-extension-point) to provide markdown support, I believe this role should be usable from markdown as well (though haven't tested it myself).
Bug 1780407 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> In terms of UX, if someone already has a searchfox permalink with revision, it seems like it would be less work for them to just use that link directly? Yeah, I think I agree here. You'd have to permalink and then cut the revision out. I wouldn't mind WONTFIXing this if a `/lastrev/` endpoint is unlikely to happen anytime soon. > so my personal recommendation to people would be to use markdown for docs since firefox-source-docs can render markdown too Note that because we use [myst](https://myst-parser.readthedocs.io/en/latest/syntax/roles-and-directives.html#roles-an-in-line-extension-point) to provide markdown support, I believe this role should be usable from markdown as well (though haven't tested it myself). Edit: Tested and using: ``` {searchfox}`<path>` ``` works in firefox-source-doc's markdown as well!