Add ability to trigger event in resolvers

[sergeyantonov1]

Summary

Added ability to trigger events in GraphQL resolvers.

Problem:

• When we use resolver we cannot make some changed in DB because GraphQL resolvers are used to read data

Case when you can use it:

• You want to track activity when user opens some page

Example of usage:

module Resolvers
  class PollItem < Resolvers::Base
    argument :id, Integer, required: true

    type Types::PollType, null: false

    private

    def fetch_data
      context[:poll] = current_user.received_polls.find(options[:id])
    end

    def trigger_event
      TriggerEvent.new(event: "poll_opened", options: { poll_id: options[:id] })
    end
  end
end

# config/initializers/events.rb
ActiveSupport::Notifications.subscribe "poll_opened" do |_name, _start, _finish, _id, payload|
  # do something
end

How it works

Test plan

None

Review notes

While reviewing pull-request (especially when it's your pull-request), please make sure that:

• you understand what problem is solved by PR and how is it solved
• new tests are in place, no redundant tests
• DB schema changes reflect new migrations
• newly introduced DB fields have indexes and constraints
• there are no missed files (migrations, view templates)
• required ENV variables added and described in .env.example and added to Heroku
• associated Heroku review app works correctly with introduced changes

Deploy notes

None

References

None

[sergeyantonov1]

@DmitryBarskov by GraphQL rules you can use query for reading data, mutation for modify data. You can read it here:

• https://graphql-ruby.org/mutations/mutation_classes.html
• https://graphql.org/learn/queries/#mutations