From 8b7abdb6cf4e15bc0b20c61435dc04f9db5d45b6 Mon Sep 17 00:00:00 2001 From: Tim Otten Date: Mon, 24 Aug 2020 02:47:22 -0700 Subject: [PATCH] CollectionAdderTrait - Use secondary ordering more akin to CRM_Core_Resources This is a very subtle behavioral change. To understand it, we must consider the traditional ordering in `CRM_Core_Resources::addScriptUrl()` and `CRM_Core_Region::add()`. Compare these two examples: ``` Civi::resources()->addScriptUrl('http://example.com/foo.js', 100, 'page-footer'); Civi::resources()->addScriptUrl('http://example.com/bar.js', 100, 'page-footer'); CRM_Core_Region::instance('page-footer')->add([ 'scriptUrl' => 'http://example.com/foo.js', 'weight' => 100, ]); CRM_Core_Region::instance('page-footer')->add([ 'scriptUrl' => 'http://example.com/bar.js', 'weight' => 100, ]); ``` You might expect this to output `