Subscription to automated resource creation
I have a question regarding subscriptions. I've set up subscriptions in my application and I have one subscription endpoint that works perfectly. I have a 2nd one that isn't working at all. However, the 2nd one monitors a resource that is created in an automated way from the backend by an ash notifier when a different resource is created.
Example: Let's pretend we have a
Message Resource and an Alert Resource. We have a Ash.Notifier that on create checks if the message has the keyword "foo". If it is, we create an Alert . If I have a subscription to the Alert resource, should I expect that subscription to work even though it wasn't created from the frontend? I would assume yes but that is not what I'm experiencing.3 Replies
As long as it is going through an ash action, it should be picked up.
I'll look into this tomorrow, if you want to help a reproduction would be highly appreciated, either as test in AshGraphql or a standalone project I can look at
Spent some time on trying to create a reproduction, but so far I haven't had much luck
Best if @lifeofdan provides one 😜
Yes, I’ll create a reproduction for this. 🙂
The bug doesn't seem to be where I thought it was so I'm also struggling to reproduce this but I will get back to you when I find where the issue lies.