Metadata
- Source
- FLUID-6729
- Type
- Bug
- Priority
- Major
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Antranig Basman
- Reporter
- Tony Atkins
- Created
2022-05-06T05:50:05.761-0400 - Updated
2024-07-22T10:35:08.552-0400 - Versions
-
- 4.0
- Fixed Versions
-
- 4.1
- Component
-
- IoC System
Description
https://github.com/fluid-project/infusion/pull/1072/files actually harbours two distinct issues. As well as FLUID-6728, the exception "Cannot read property 'composeSegments' of undefined" is received when attempting to store any {sourcePath} value in the model. fluid.parseValidModelReference is unprepared for the case where the context target is not a component, and instead assumes that it must be a component with an applied.
fluid.parseValidModelReference = function (that, name, ref, permitNonModel) {
....
parsed.path = target && target.applier.composeSegments.apply(null, parsed.modelSegs);
}
We get here and target has been fully resolved to the referent of sourcePath, e.g. in the test case "coffee", so we have parsed.that of "coffee" and parsed.path = "". Since parsed.nonModel is correctly set to true, there won't be a further problem passing this odd reference out of the system.