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
Today we always generate a clickable link for F# compiler diagnostics that have a code - even when there is no matching page for the diagnostic.
FSAC should instead only create such a link if the link exists and is resolvable. To determine this, FSAC should build a one-per-process cache that checks the generate link for a given diagnostic code by sending an httpclient request (following redirects, etc) and verifying if that result returns a 2xx-level status code.
For super bonus points, this cache would be persistable and shareable across sessions (perhaps via some kind of FSAC workspace-based cache - VSCode for example gives each extension a workspace-specific cache directory that could be passed in as a command-line argument to provide a safe cache location, defaulting to some workspace-root-local or user-local location?).
Checklist
I have looked through existing issues to make sure that this feature has not been requested before
I have provided a descriptive title for this issue
I am aware that even valid feature requests may be rejected if they do not align with the project's goals
I or my company would be willing to contribute this feature