Redundancy in Firefox extension settings code?

[musjj]

I'm trying to understand this part of this code:

home-manager/modules/programs/firefox/mkFirefoxModule.nix

Lines 1005 to 1015 in 12fa854

	(mkMerge (
	mapAttrsToList (
	name: settingConfig:
	mkIf (settingConfig.settings != { }) {
	"${cfg.profilesPath}/${profile.path}/browser-extension-data/${name}/storage.js" = {
	force = settingConfig.force || profile.extensions.force;
	text = lib.generators.toJSON { } settingConfig.settings;
	};
	}
	) profile.extensions.settings
	))

As far as I can tell, to set profile.extensions.settings.${addonId}.settings you also need to set profile.extensions.force to true, due to this assertion:

home-manager/modules/programs/firefox/mkFirefoxModule.nix

Lines 792 to 802 in 12fa854

	assertions = [
	(mkNoDuplicateAssertion config.containers "container")
	{
	assertion = !(extensionSettingsNeedForce config.extensions.settings) || config.extensions.force;
	message = ''
	Using '${lib.showOption profilePath}.extensions.settings' will override all
	previous extensions settings. Enable
	'${lib.showOption profilePath}.extensions.force' to acknowledge this.
	'';
	}
	]

So the settingConfig.force || profile.extensions.force above will practically always evaluate to true, regardless of the individual extension's force setting.