Metadata
- Source
- FLUID-5912
- Type
- Bug
- Priority
- Blocker
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Antranig Basman
- Reporter
- Alan Harnum
- Created
2016-05-31T14:32:10.729-0400 - Updated
2024-07-22T10:35:27.809-0400 - Versions
- N/A
- Fixed Versions
-
- 4.0
- Component
-
- Framework
Description
Based on the example at http://docs.fluidproject.org/infusion/development/SubcomponentDeclaration.html#dynamic-subcomponents-with-a-source-event, it should be possible to use the context name "{arguments}" to refer to "the argument list that was used to fire the event which triggered the creation of the particular dynamic subcomponent".
This currently fails within a model options block because the framework interprets {arguments} as an implicit model relay to a nonexistent component if found within model options.
The recommended workaround at this time is to put any {arguments} references in a plain options area and then refer to that from the model.
—
IRC conversation about the issue: https://botbot.me/freenode/fluid-work/2016-05-31/?msg=67028698&page=2
Gist with example code at https://gist.github.com/waharnum/8c1abcbec3f9786c899f9e6637564c8c
Comments
-
Justin Obara commented
2017-05-29T10:54:38.057-0400 I'm also finding a similar issue with trying to use the "{arguments}" context name in a members block.
see: https://botbot.me/freenode/fluid-work/2017-05-29/?msg=86288307&page=1
-
Antranig Basman commented
2017-11-08T12:34:47.018-0500 Wow, I can't believe this didn't get fixed... must have fallen into an informational black spot ...
-
Tony Atkins [RtF] commented
2018-01-12T11:46:55.336-0500 This also happens within member blocks, as demonstrated here:
https://gist.github.com/the-t-in-rtf/6a85c3cf9676d227748a20180a09b929
-
Antranig Basman commented
2019-09-30T09:16:21.436-0400 This is now fixed in the FLUID-6148 branch https://github.com/fluid-project/infusion/pull/824