[Ignore] Individual page diagnostic proof of concept #4560
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This a really rough and hacky proof of concept exploring the possibility of each diagnostic being on its own page to see if it's a direction we want to go. If it is a direction we want to go, I will rewrite this setup and code to be much cleaner and performant, and also make the necessary changes in analyzer to make this process easier.
tools/diagnostics
./tools/diagnostics/diagnostic_name
such as `tools/diagnostics/conflicting_constructor_and_static_member.<wbr />
after underscores in the page h1 header, as the diagnostic names were too long and going off the page.tools/diagnostic-messages
, but has the following modifications:/tools/diagnostic-messages#conflicting_constructor_and_static_member
for an example of the redirect working