Open rafagalan opened 2 years ago
Thanks @rafagalan - making sure I understand your use case, you would like to be able to listen for new events? I don't know if it makes sense to bake that into the subgraph definition, but we do definitely want to enable subscription type use cases, where users can subscribe to entity changes cc @dotansimha
Jepp in mind that there are complications around verifiability with subscriptions. The easiest way is too implement them with polling in the client side. Native GraphQL subscriptions in graph-node exist but are likely a dead end.
And is there any estimation on when this (#2953) could be fixed? We will have to stick with polling for the moment, although not ideal.
Do you want to request a feature or report a bug? Feature
What is the current behavior? Whenever an event is detected the node just executes the mapping.
Desired behavior? It would be nice if the yaml definition had a param to indicate the node to make a request to a given url, this way the node could be integrated with more services giving some users a finer UX.