About "dub.json is now checked" change

[ryuukk]

Since we can't comment anything, it makes experimenting or testing configurations very hard, you have to remove things and hopefully remember what you removed once you finish experiment

I was using that as a feature to temporarily mute certain lines with underscore '_'

Don't get me wrong, it's a needed change, but i worry it'll turn into an error in the future, so i'm just anticipating

#2501

[Geod24]

As a side note, Discussions would be a better medium than an issue here. Or comment on the PR.
As for comment, it's definitely a problem I intend to solve in the next 10 releases (2 years!).

[WebFreak001]

we had discussions about the fields before and listed all non-conforming keys in public packages, but don't want to make them error. Warnings should always be enough for users, if they use something that doesn't work they can see it in a nice visible warning and fix it or keep it during development.

[Geod24]

Indeed, the original idea was to make those errors, but that was before the ability to make them warning existed, I believe.

[Geod24]

@WebFreak001 : Actually thinking more about this, I'm not 100% sure keeping them as warnings is a good thing.
You might not always see it, e.g. imagine having a CI job which tests with the last 10 versions of the compiler but having only warnings displayed here...