Previously, if the develwarn call site did not specify the category of warning,
and devel.all-warnings was False, it would emit the warning. If it was
intended that this emit a warning if config is unspecified, I would have
expected a comment, so I assumed this was unintentional and am changing the
behavior.
Details
Details
- Reviewers
yuja - Group Reviewers
hg-reviewers - Commits
- rHGfa2395db68c6: develwarn: do not emit warning if "config" is unspecified
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Event Timeline
Comment Actions
(Specifically picked yuja as reviewer since they reviewed the original https://www.mercurial-scm.org/repo/hg/rev/3f33831a9202, so hopefully can tell me whether this was intentional or not and I'm possibly breaking stuff with this change :))
Comment Actions
(Specifically picked yuja as reviewer since they reviewed the original
https://www.mercurial-scm.org/repo/hg/rev/3f33831a9202,
so hopefully can tell me whether this was intentional
I think it was intentional during the migration to the config gating API,
i.e. no gating unless config= is specified, but the current behavior is
weird, and should be worth breaking the old API.