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
From #105: it could be helpful to add the expected (parsed) location of a type to the resolve warning for users. In the linked issue it's not really clear whether autolink has parsed the correct target and not resolved, or failed altogether, or if the fault is in the generated documentation instead. Displaying the expected location would allow users to verify that a sequence of statements has been parsed correctly and thus narrow down the cause or provide more information when submitting a bug report.
We provide the key in missing inventory warnings. This would be akin to that, except that we don't actually know the key so we have to take a step back.
The text was updated successfully, but these errors were encountered:
From #105: it could be helpful to add the expected (parsed) location of a type to the resolve warning for users. In the linked issue it's not really clear whether autolink has parsed the correct target and not resolved, or failed altogether, or if the fault is in the generated documentation instead. Displaying the expected location would allow users to verify that a sequence of statements has been parsed correctly and thus narrow down the cause or provide more information when submitting a bug report.
We provide the key in missing inventory warnings. This would be akin to that, except that we don't actually know the key so we have to take a step back.
The text was updated successfully, but these errors were encountered: