Option columnDefs: targets conflict resolution

fgeorges

Hi,

The targets entry with the value _all can be used to set a default. But how are "conflicts" resolved? For instance, if each item in the array is applied in sequence, the following "default" will override the previous definition:

columnDefs: [
   { targets: 'num',  type: 'num' },
   { targets: '_all', type: 'string' }
]

Is there a positional preference? Or maybe some target kinds take precedence over others? (like _all getting the least priority).

PS: I initially posted this as a comment on the page for columnDefs. Sorry for the noise.

Regards, --Flo

allan

Hi Flo,

Thanks for noting this. I've just committed a change for the documentation than includes conflict resolution information and will deploy it to the site soon (probably Monday).

Basically, the higher the order in the array, the higher priority.

Regards,
Allan

fgeorges

Thank you for the quick response and action!