id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	focuses
36167	Improve alignment between settings params between Customizer Controls and Partials	westonruter	westonruter	"In #27355, the concept of a `Partial` was introduced and is analogous to a `Control` in many ways, particularly in that it an object associated with one or more settings. A control is instantiated in JS like:

{{{#!js
var control = new wp.customize.Control( 'foo', {
    params: {
        setting: 'default',
        settings: { 'default': 'foo', 'bar': 'bar' },
    }
});
}}}

Whereas a partial is instantiated like: 

{{{#!js
var control = new wp.customize.Partial( 'foo', {
    params: {
        settings: [ 'foo', 'bar' ],
        primarySetting: 'foo'
    }
});
}}}

Note the difference in how a partial uses `primarySetting` to designate the main setting for a control, whereas a control has a secondary “setting key” which is used identify which of the settings in the object passed should be the main setting.

Personally, the way `settings` are passed to Controls is not very intuitive to me, but to improve the parity in the API, perhaps both styles should be accepted by the partial."	enhancement	closed	low	4.9	Customize	4.6	normal	fixed	has-dev-note