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
In your example usage [This is the example-term](./terms/example-term), the path is relative. I've tried [This is the example-term](/terms/example-term), which doesn't seem to trigger the popover (though the link works).
We pretty much always prefer to use absolute paths, or we find we move content around and everything breaks. Is it intentional that only relative paths are parsed?
The text was updated successfully, but these errors were encountered:
Hi, in order to make sure that we can reproduce the issue that you are having, it would really help us if you'd share your docusaurus.config.js and package.json.
As a general remark, you can configure the paths for terms and docs in the plugin options, maybe that is something that would help if you haven't tried this already.
In your example usage
[This is the example-term](./terms/example-term)
, the path is relative. I've tried[This is the example-term](/terms/example-term)
, which doesn't seem to trigger the popover (though the link works).We pretty much always prefer to use absolute paths, or we find we move content around and everything breaks. Is it intentional that only relative paths are parsed?
The text was updated successfully, but these errors were encountered: