config: use level to properly deal with value priority
Needs ReviewPublic
Actions

Authored by marmoute on Fri, Jan 29, 8:40 PM.

Details

Reviewers

Alphare

Group Reviewers

hg-reviewers

Summary

A higher priority alias will now take precedence over lower priority ones.

This was a requirements step before using alias more widely, especially to
rename existing and established config option.

Repository

rHG Mercurial

Branch

default

Lint

No Linters Available

Unit

No Unit Test Coverage

Alphare added inline comments.

tests/test-config.t
478–479	Should this comment be dropped now?

tests/test-config.t
478–479	good catch, it should. (dropped in latest version).

✅ refresh by Heptapod after a successful CI run (🐙 💚)

			Path	Packages
M			mercurial/ui.py (13 lines)
M			tests/test-config.t (14 lines)

Status	Author	Revision
Closed	marmoute	D9923 config: use the right API to access git-submodule
Closed	marmoute	D9922 config: use the right API to access template access
Closed	marmoute	D9921 config: use the right API to access subrepository section
Needs Review	marmoute	D9927 config: use level to properly deal with value priority
Needs Review	marmoute	D9926 config: track the "level" of a value
Needs Review	marmoute	D9925 config: track "source" along side value
Needs Review	marmoute	D9924 config: use a new `alter` method in `fixconfig`
Closed	marmoute	D9920 config: test priority involving alias and cli
Closed	marmoute	D9919 config: test priority involving alias and include
Closed	marmoute	D9918 config: test priority involving alias
Closed	marmoute	D9917 config: test priority involving the command line
Closed	marmoute	D9916 config: test priority involving include
Closed	marmoute	D9915 config: add a test for priority when includes are involved