FLUID-4634: Demands for boiled events will collide if they share any context values.

Description

If multiple components use the same name for a boiled event, the arguments specified in a demands block will collide if they share any of the same context. Meaning that in all instances the same demands block will be used to resolve the demanded options for the event.

Attachments

• FLUID-4634.patch

Comments

• Justin Obara commented 2012-03-05T09:00:04.255-0500

  FLUID-4634.patch provides unit tests that demonstrate this issue.

  You can also find the unit tests in a branch in my github repo:
  https://github.com/jobara/infusion/tree/FLUID-4634

• Antranig Basman commented 2012-05-09T03:15:11.494-0400

  Hi Justin - unfortunately this is currently "expected behaviour" due to the way context matching rules were implemented. As explained in FLUID-4707 it would currently cause too much upheaval to rewrite these rules due to the change in meaning of a large number of already written demands blocks, so we will have to live with it until the framework is rewritten wholesale for FLUID-4392. In the meantime, a workaround would be to issue a contradicting demands block with no contexts which will still take priority over your block in mismatched situations - for example in your case you ought to be able to have success by writing

  fluid.demands("testDemandedEvent", [], ["{arguments}.0"]);

  which will take priority in all mismatching situations. Please could you rewrite your test case so that it cleans up the static environment (in a finally block) before it concludes - you can see examples of this style in FluidIoCTests.js

• Justin Obara commented 2012-05-09T10:44:57.808-0400

  Thanks for looking at this Antranig. I've updated the test case to clean up the static environment. I put the test functions into a try block, with the code to delete the property from the static environment in the finally block.

• Antranig Basman commented 2013-03-06T01:31:18.121-0500

  Fixed along with FLUID-4707 by merge at 91d5d1