favonia

@kentookura You need to explicitly access the state with all the accumulated diagnostics. The state should be made available after calling `Reporter.run`.

@kentookura I'm not sure about reordering diagnostics, but it seems trivial to implement some inefficient suppression. This can also be used to stop the same hint from being displayed, etc....

@kentookura I'm repurposing this issue for the common need I saw in https://github.com/mikeshulman/narya/pull/24: suppressing useless diagnostics caused by already reported errors.

@kentookura @mikeshulman If we want a "universal" index type of "causes", what should it be? Or should we avoid such a "universal" type at all costs?

@kentookura I meant, using your example, how would you write down "A" in some "global database" so that you know it has been reported when checking "B"?

Hi! Thanks for opening the issue. The environment variable name for secrets should be `CLOUDFLARE_API_TOKEN_FILE` instead of `CLOUDFLARE_API_TOKEN`. Do you think there's something we can change in README to clarify...

@NotaInutilis You are not the only one tripping over the expandable descriptions. I now think I should remove all of the folding.

@samumakinen Thanks for the suggestion. After further investigation, I now see that Chrome-based browsers will expand the folds automatically but Firefox and Safari will not. :thinking: Let's open another ticket...

@tchar Thanks for the suggestion! This is on my radar (e.g., #1016) but I cannot seem to come up with a good design for environment variables. It seems we are...

@tchar I think I would prefer the first approach, but it requires more careful thought than I can afford right now. I hope the workaround isn't consuming too many resources...