Attached is a test case which shows that duplicating a cfc instance seems to result in a struct that then cfdump won’t expand.
I’ve tried to base this on issue we are seeing in the app where the method would not be found on the duplicated instance when we try to call the setinvocation method on the cloned instance. This test case isn’t perfect but hopefully it makes sense.
I found also that cfdump vas blowing up on the actual app when I tried to dump the cloned cfc, it doesn’t do that on the test instance so might have actually been a very large error markup.
Attachments
1
Activity
Show:
Brad Wood October 30, 2024 at 4:28 AM
Ok, I don’t know if it’s perfect, but my tests are passing. Let me know if it works.
Brad Wood October 30, 2024 at 3:43 AM
Our duplicate BIF doesn’t have any logic for handling CFCs in it yet, so it just treats it like a struct, since it is one after all. We need to code to handle this.
Alex Skinner October 29, 2024 at 8:52 PM
If you do call a method like setInvocation it will complain about this not being found but it is a duplicate of an instantiated component so it should exist I think
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Hi,
Attached is a test case which shows that duplicating a cfc instance seems to result in a struct that then cfdump won’t expand.
I’ve tried to base this on issue we are seeing in the app where the method would not be found on the duplicated instance when we try to call the setinvocation method on the cloned instance. This test case isn’t perfect but hopefully it makes sense.
I found also that cfdump vas blowing up on the actual app when I tried to dump the cloned cfc, it doesn’t do that on the test instance so might have actually been a very large error markup.