Metadata
- Source
- FLUID-6129
- Type
- Bug
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- N/A
- Reporter
- Antranig Basman
- Created
2017-02-13T18:55:34.782-0500 - Updated
2021-07-29T01:50:08.043-0400 - Versions
-
- 2.0
- 2.1
- 3.0
- Fixed Versions
-
- 5.0
- Component
-
- Data Binder
- IoC System
Description
The source tracking system for ChangeApplier-mediated changes described at http://docs.fluidproject.org/infusion/development/ChangeApplierAPI.html#source-tracking-and-filtering-in-model-listener-blocks has a configurational hole - despite FLUID-5490 ensuring that change sources will cascade through back-to-back model listeners, this has been done via an implementational "back door" that is not possible to address via a context name in a listener definition.
It appears that the back door, implemented in fluid.resolveModelListener, DataBinding.js line 957, used a specially named record mergeRecord to avoid polluting the existing context name source which is used by dynamic components. We should just stick a "sources" entry into the change argument which is already resolved, since otherwise the only route is to invite the user to look into the undocumented argument transaction.