`lazy` with mutliple html composition layers appears to cause runtime errors / other odd behavior about purescript-flame HOT 6 CLOSED

Hello @abradley2 ,

Thanks for submitting this issue with a minimal example. Upon running it, there is indeed something broken. I will look into figuring what exactly as soon as possible.

from purescript-flame.

I tried this out on the isolated example and it did fix the issue. However in our larger application we're still seeing failed pattern matches on the patched version due to messages not mapping correctly. I'm working on isolating the example to figure out what's going on

from purescript-flame.

@abradley2 could you please point your version to a50478d? It should be fixed, but right now I don't have any complex projects to test it out on.

from purescript-flame.

@BusinessTony if the application is open source or if you can put an isolated example online, I can take a look at it to try and help narrow down the problem.

from purescript-flame.

@easafe it's not open source unfortunately and I wasn't able to figure out how to isolate the offending code in a way where the issue persisted- I'm not sure what was happening 🤷 . However the additional issue I was describing has ceased to turn up after some unrelated refactoring, we've been on a50478d for weeks and not seen any issues and have been using lazy successfully. I think we're good 👍

from purescript-flame.

Sounds good to me!

from purescript-flame.