Ruby Developer Guide
Other documentationsDemoCommunityGitHub
  • Forest Admin
  • Getting started
    • How it works
    • Quick start
      • Ruby on Rails
    • Create your agent
    • Troubleshooting
    • Migrating legacy agents
      • Pre-requisites
      • Recommendations
      • Migration steps
      • Code transformations
        • API Charts
        • Live Queries
        • Smart Charts
        • Route overrides
        • Smart Actions
        • Smart Fields
        • Smart Relationships
        • Smart Segments
  • Data Sources
    • Getting Started
      • Collection selection
      • Naming conflicts
      • Query interface and Native Queries
        • Fields and projections
        • Filters
        • Aggregations
    • Provided data sources
      • ActiveRecord
        • Polymorphic relationships
      • Mongoid
    • Write your own
      • Translation strategy
        • Structure declaration
        • Capabilities declaration
        • Read implementation
        • Write implementation
        • Intra-data source Relationships
      • Contribute
  • Agent customization
    • Getting Started
    • Actions
      • Scope and context
      • Result builder
      • Static Forms
      • Widgets in Forms
      • Dynamic Forms
      • Form layout customization
      • Related data invalidation
    • Charts
      • Value
      • Objective
      • Percentage
      • Distribution
      • Leaderboard
      • Time-based
    • Fields
      • Add fields
      • Move, rename and remove fields
      • Override binary field mode
      • Override writing behavior
      • Override filtering behavior
      • Override sorting behavior
      • Validation
    • Hooks
      • Collection hook
      • Collection override
    • Pagination
    • Plugins
      • Write your own
    • Relationships
      • To a single record
      • To multiple records
      • Computed foreign keys
      • Under the hood
    • Search
    • Segments
  • Frontend customization
    • Smart Charts
      • Create a table chart
      • Create a bar chart
      • Create a cohort chart
      • Create a density map
    • Smart Views
      • Create a Map view
      • Create a Calendar view
      • Create a Shipping view
      • Create a Gallery view
      • Create a custom tinder-like validation view
      • Create a custom moderation view
  • Deploying to production
    • Environments
      • Deploy on AWS
      • Deploy on Heroku
      • Deploy on GCP
      • Deploy on Ubuntu
    • Development workflow
    • Using branches
    • Deploying your changes
    • Forest Admin CLI commands
      • init
      • login
      • branch
      • switch
      • set-origin
      • push
      • environments:create
      • environments:reset
      • deploy
  • Under the hood
    • .forestadmin-schema.json
    • Data Model
      • Typing
      • Relationships
    • Security & Privacy
Powered by GitBook
On this page
  • Tips
  • Count queries

Was this helpful?

  1. Data Sources
  2. Write your own
  3. Translation strategy

Read implementation

This is the official documentation of the agent_ruby Ruby agent.

Developing your query translation layer is much easier when you can preview your work and have intermediary deliverables.

Emulation comes to the rescue: all features that need to be implemented when making a translating data source can be emulated inside your Node.js, at the cost of performance.

This enables you to be up and running in minutes and then optimize your code as you go.

require 'httparty'

module App
  module Collections
    class MyCollection < ForestAdminDatasourceToolkit::Collection
      include ForestAdminDatasourceToolkit::Schema
      # [... Declare structure and capabilities]

      def list(caller, filter, projection)
        # Fetch all records on all requests (this is _very_ inefficient)
        response = HTTParty.get('https://my-api/my-collection')
        result = response.parsed_response['items']

        if filter.condition_tree
          result = filter.condition_tree.apply(response, self, caller.timezone)
        end

        if filter.sort
          result = filter.sort.apply(result)
        end

        if filter.page
          result = filter.page.apply(result)
        end

        if filter.segment
          raise 'This collection does not implement native segments'
        end

        if filter.search
          raise 'This collection is not natively searchable'
        end

        projection.apply(result)
      end

      def aggregate(caller, filter, aggregation, limit = nil)
        # Fetch all records which should be aggregated
        records = list(caller, filter, aggregation.projection)

        # Use "in-process emulation" to aggregate the results
        aggregation.apply(records, caller.timezone, limit)
      end
    end
  end
end

Tips

Count queries

The aggregate method is used by Forest Admin both to count records and to extract the data which is needed to generate charts.

If the API/Database you are targeting has an efficient API that is made for counting records, you may want to handle this case first.

require 'httparty'

module App
  module Collections
    class MyCollection < ForestAdminDatasourceToolkit::Collection
      include ForestAdminDatasourceToolkit::Schema
      # [... Declare structure, capabilities and list method]

      def aggregate(caller, filter, aggregation, limit = nil)
        if aggregation.operation == 'Count' && aggregation.groups.empty? && !aggregation.field
          return [{ 'value' => count(caller, filter) }]
        end

        # [... handle the general case]
      end

      def count(caller, filter)
        response = HTTParty.get('https://my-api/my-collection/count', query: { filter: translate_filter(caller, filter) })

        JSON.parse(response.body)['count']
      end

      private

      def translate_filter(caller, filter)
        # [... translate filter]
      end
    end
  end
end
PreviousCapabilities declarationNextWrite implementation

Last updated 4 months ago

Was this helpful?