# When You Need a Ruby Data Structure that Responds to Method Calls - Use OpenStruct

DevFeed: [When You Need a Ruby Data Structure that Responds to Method Calls - Use OpenStruct](<https://devfeed.tech/articles/when-you-need-a-ruby-data-structure-that-responds-to-method-calls-use-openstruct-28305.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/ruby/2020/02/09/when-you-need-a-ruby-data-structure-that-responds-to-method-calls-use-openstruct.html>)

Author: Fuzzygroup

Published: 2020-02-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Ruby](<https://devfeed.tech/topics/ruby.md>), [Data structures](<https://devfeed.tech/topics/data-structures.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [data-structure](<https://devfeed.tech/tags/data-structure.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [open-struct](<https://devfeed.tech/tags/open-struct.md>), [rails](<https://devfeed.tech/tags/rails.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [standard-library](<https://devfeed.tech/tags/standard-library.md>)

## AI overview

A Ruby developer uses OpenStruct to simulate an API response while a server-side component needs configuration data before the real API is available. The article explains that OpenStruct supports dot-method access and belongs to Ruby's standard library, with a require needed in pure Ruby.

## Source excerpt

I'm in the position of building a system where there is one source of truth for configuration - an API from the the user interface component of the system (this is the part that will always be online so it made sense for it to serve the api). The problem is that I have a server side component that needs to go online today as in now. And that API isn't yet available. I basically have a section in my code where I get the configuration data. My normal approach is to create a ruby Mechanize object and do a page fetch against the configuration API. This returns a response object with a .body method that can be parsed something like this: response = agent.get(dest_url) JSON.parse(response.body) My means of working around this without an API is to use an OpenStruct as follows: response = OpenStruct.new response.body = '{ "kafka_servers":["b-2.AAA.ccc.c4.kafka.us-east-2.amazonaws.com:9092","b-1.BBB.ccc.c4.kafka.us-east-2.amazonaws.com:9092"]}' JSON.parse(response.body) OpenStruct is a hash like data structure that responds to ruby dot messages so my "response" object above in the second code block will respond to ".body". Overall OpenStructs are a very, very useful tool for this type of pseudo mocking behavior. Note: OpenStruct is built into Rails so you can just a "response = OpenStruct.new" at any point. If you are building pure Ruby software then you need to first require it with: require 'ostruct' and then use it with "response = OpenStruct.new". There is no Gem component to use OpenStruct - it is a part of the Ruby standard library but it isn't available until you do a require.