monday_ruby 1.1.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fca12fa6b3f49d85bea9353e7621904cbe773f69fc9b4b18afc641a7c25318a0
-  data.tar.gz: 738fa89ae3732c0bf6afe22c314d7dcc42bae2990bfc313e640ce8aee7183755
+  metadata.gz: 3837300eeee4b5c5fc64a1c69eccc897cbbf57dc05acfaba3163bd67d1d1beb8
+  data.tar.gz: c0164784b3ec5b9780e735082e47f5f6381d8b115a11310addb707c046b84f0d
 SHA512:
-  metadata.gz: 843ba4a79d3a53b75b8ddfc8eb545d442600fe3b5b90df4f01ced08dd1516c8e9aab4755180b094d7c8fa94a2c330497dbee0b86ecc04071101deb0e236d2d6c
-  data.tar.gz: e6a6b8a7c1b912aee79a55f3da44372cf4d35eed207c7e061f131e6385ed9c48475c87c5722162dbdbf259058eaf13f7acf0e990a765dbc3b33299662120d8ef
+  metadata.gz: fb6897aa4cb9810db87e09f0d70a9614d01cc5685c1cd5992780c0838e6f5a84444d430ad20454dd1a144d897a037fb84dc40b2cc9fb88289222f3a5cad7860a
+  data.tar.gz: 5642bf287741d7d3464142e5a4c78ce8d9da29be8ded5f9849820e6b6112258e8f3a8273618388c656649b89ba9d426106b91595e9f188c8ea1fb9d89c54f895

data/CHANGELOG.md

@@ -1,3 +1,27 @@
+## v1.2.1 (January 23, 2026)
+
+### Fixed
+
+- Fixed issue where any string containing a dollar sign was incorrectly treated as a GraphQL variable.
+
+### Changed
+
+- Updated `base64` dependency requirement from `~> 0.2.0` to `>= 0.2, < 0.4` for broader compatibility.
+
+## v1.2.0 (November 18, 2025)
+
+#### Added
+
+- Added support for adding Files (Assets) to a File column.
+- Added support for adding Files (Assets) to an Update (Comments).
+- Added helper method for clearing a Files column.
+
+#### Changed
+
+- Updated gemspec dependency to use multipart-post (~> 2.4.0)
+- Updated rubocop RSpec/MultipleMemoizedHelpers from 10 to 11.
+- Updated Utils to allow GraphQL variables in queries.
+
 ## v1.1.0 (October 27, 2025)
 
 ### Added

data/README.md

@@ -1,240 +1,244 @@
-# Monday API Library for Ruby
+# monday_ruby
 
 ![Build Status](https://github.com/sanifhimani/monday_ruby/actions/workflows/ci.yml/badge.svg)
 [![Gem Version](https://badge.fury.io/rb/monday_ruby.svg)](https://badge.fury.io/rb/monday_ruby)
 [![Coverage Status](https://coveralls.io/repos/github/sanifhimani/monday_ruby/badge.svg?branch=main)](https://coveralls.io/github/sanifhimani/monday_ruby?branch=main)
 
-This library provides convenient access to the monday.com API from the application written in Ruby.
+A Ruby client library for the [monday.com GraphQL API](https://developer.monday.com/api-reference). Build integrations with boards, items, columns, and more using idiomatic Ruby.
 
-The library provides:
+## Features
 
-1. A pre-defined set of methods to easily interact with the API resources.
-2. Easy configuration path for fast setup and use.
-3. Easy error handling.
+- **Resource-based API** - Clean, intuitive interface (`client.board.query`, `client.item.create`)
+- **Flexible configuration** - Global or per-client setup
+- **Comprehensive error handling** - Typed exceptions for different error scenarios
+- **Cursor-based pagination** - Efficiently handle large datasets
+- **Fully tested** - 100% test coverage with VCR-recorded fixtures
 
-**Check out the [Wiki](https://github.com/sanifhimani/monday_ruby/wiki) for detailed documentation on how to use the library.**
+## Documentation
 
-## Installation
+**[Complete Documentation →](https://sanifhimani.github.io/monday_ruby/)**
 
-```bash
-gem install monday_ruby
-```
+- [Getting Started Tutorial](https://sanifhimani.github.io/monday_ruby/tutorial/first-integration)
+- [How-to Guides](https://sanifhimani.github.io/monday_ruby/guides/installation)
+- [API Reference](https://sanifhimani.github.io/monday_ruby/reference/client)
+- [Best Practices](https://sanifhimani.github.io/monday_ruby/explanation/best-practices/errors)
 
-## Usage
+## Installation
 
-***Complete list of resources along with examples are provided in the [Wiki](https://github.com/sanifhimani/monday_ruby/wiki).***
+Add to your Gemfile:
 
-The library needs to be configured with your account's authentication token which is available on the Admin tab on monday.com. Elaborate documentation can be found [here](https://developer.monday.com/api-reference/docs/authentication).
+```ruby
+gem "monday_ruby"
+```
 
-### Configuration
+Or install directly:
 
-Once you have the authentication token, you can either globally configure the library or you can configure a specific client.
+```bash
+gem install monday_ruby
+```
 
-#### Global config
+## Quick Start
 
 ```ruby
 require "monday_ruby"
 
+# Configure with your API token
 Monday.configure do |config|
-  config.token = "<AUTH_TOKEN>"
+  config.token = ENV["MONDAY_TOKEN"]
 end
-```
 
-#### Client specific config
-```ruby
-require "monday_ruby"
+# Create a client
+client = Monday::Client.new
 
-client = Monday::Client.new(token: "<AUTH_TOKEN>")
+# Query boards
+response = client.board.query(args: { limit: 5 })
+
+if response.success?
+  boards = response.body.dig("data", "boards")
+  boards.each { |board| puts board["name"] }
+end
 ```
 
-The version configuration field allows you to optionally pass in the version of the API you want to use. By default, the latest stable version is used.
+Get your API token from your [monday.com Admin settings](https://support.monday.com/hc/en-us/articles/360005144659-Does-monday-com-have-an-API).
 
-```ruby
-require "monday_ruby"
+## Usage
 
-Monday.configure do |config|
-  config.token = "<AUTH_TOKEN>"
-  config.version = "2023-07"
-end
-```
+### Configuration
 
-You can also configure request timeouts (new in v1.1.0):
+**Global configuration** (recommended):
 
 ```ruby
-require "monday_ruby"
-
 Monday.configure do |config|
-  config.token = "<AUTH_TOKEN>"
-  config.open_timeout = 10  # seconds (default: 10)
-  config.read_timeout = 30  # seconds (default: 30)
+  config.token = ENV["MONDAY_TOKEN"]
+  config.version = "2024-01"  # API version (optional)
 end
 
-# Or configure per client
-client = Monday::Client.new(
-  token: "<AUTH_TOKEN>",
-  open_timeout: 15,
-  read_timeout: 45
-)
+client = Monday::Client.new
 ```
 
-### Accessing a response object
-
-Get access to response objects by initializing a client and using the appropriate action you want to perform:
+**Per-client configuration**:
 
 ```ruby
-client = Monday::Client.new(token: "<AUTH_TOKEN>")
-response = client.boards
-
-puts response.success?
-puts response.body
+client = Monday::Client.new(
+  token: ENV["MONDAY_TOKEN"],
+  version: "2024-01"
+)
 ```
 
-### Use cases
-
-Here are some common use cases for the API client.
-
-#### Fetching all the boards
-
-Initialize the client with the auth token and call the `boards` method.
+**Configure timeouts**:
 
 ```ruby
-client = Monday::Client.new(token: <AUTH_TOKEN>)
-
-response = client.boards # => <Monday::Response ...>
-
-# To check if the request was successful
-response.success? # => true
-
-# To get the boards from the response
-response.body.dig("data", "boards") # => [...]
+Monday.configure do |config|
+  config.token = ENV["MONDAY_TOKEN"]
+  config.open_timeout = 10  # seconds (default: 10)
+  config.read_timeout = 30  # seconds (default: 30)
+end
 ```
 
-#### Creating a new board
-
-Initialize the client with the auth token and call the `create_board` method.
+### Working with Boards
 
 ```ruby
-client = Monday::Client.new(token: <AUTH_TOKEN>)
-
-args = {
-  board_name: "Test board",
-  board_kind: "public",
-  description: "Test board description"
-}
+# Query boards
+response = client.board.query(
+  args: { ids: [1234567890] },
+  select: ["id", "name", "description"]
+)
 
-# => <Monday::Response ...>
-response = client.create_board(args: args)
+boards = response.body.dig("data", "boards")
 
-# To check if the request was successful
-response.success? # => true
+# Create a board
+response = client.board.create(
+  args: {
+    board_name: "Project Tasks",
+    board_kind: "public",
+    description: "Track project deliverables"
+  }
+)
 
-# To get the created board from the response
-response.body.dig("data", "create_board") # => { ... }
+board = response.body.dig("data", "create_board")
 ```
 
-#### Creating a new item on board
-
-Initialize the client with the auth token and call the `create_item` method.
+### Working with Items
 
 ```ruby
-client = Monday::Client.new(token: <AUTH_TOKEN>)
-
-args = {
-  board_id: <BOARD_ID>,
-  item_name: "New item",
-  column_values: {
-    status: {
-      label: "Working on it"
-    },
-    keywords: {
-      labels: ["Tech team", "DevOps team"]
+# Create an item
+response = client.item.create(
+  args: {
+    board_id: 1234567890,
+    item_name: "Implement authentication",
+    column_values: {
+      status: { label: "Working on it" },
+      date4: { date: "2024-12-31" }
     }
   }
-}
-
-# => <Monday::Response ...>
-response = client.create_item(args: args)
+)
 
-# To check if the request was successful
-response.success? # => true
+# Query items
+response = client.item.query(
+  args: { ids: [987654321] },
+  select: ["id", "name", { column_values: ["id", "text"] }]
+)
 
-# To get the created item from the response
-response.body.dig("data", "create_item") # => { ... }
+items = response.body.dig("data", "items")
 ```
 
-#### Fetching items with pagination (New in v1.1.0)
+### Pagination
 
-The library now supports efficient cursor-based pagination for retrieving large numbers of items. This is the recommended approach for working with boards, groups, or items that contain many records.
+Handle large datasets efficiently with cursor-based pagination:
 
 ```ruby
-client = Monday::Client.new(token: <AUTH_TOKEN>)
-
-# Fetch first page of items from a board (up to 500 items per page)
+# Fetch first page
 response = client.board.items_page(
-  board_ids: <BOARD_ID>,
+  board_ids: 1234567890,
   limit: 100
 )
 
-# Extract items and cursor from response
 items = response.body.dig("data", "boards", 0, "items_page", "items")
 cursor = response.body.dig("data", "boards", 0, "items_page", "cursor")
 
-# Fetch next page using cursor
+# Fetch next page
 if cursor
   next_response = client.board.items_page(
-    board_ids: <BOARD_ID>,
+    board_ids: 1234567890,
     limit: 100,
     cursor: cursor
   )
 end
-
-# You can also filter items using query_params
-response = client.board.items_page(
-  board_ids: <BOARD_ID>,
-  limit: 50,
-  query_params: {
-    rules: [{ column_id: "status", compare_value: [1] }],
-    operator: :and
-  }
-)
 ```
 
-Pagination is also available for groups and items:
+See the [Pagination Guide](https://sanifhimani.github.io/monday_ruby/guides/advanced/pagination) for more details.
 
-```ruby
-# Fetch paginated items from a group
-response = client.group.items_page(
-  board_ids: <BOARD_ID>,
-  group_ids: "group_id",
-  limit: 100
-)
+### Error Handling
 
-# Fetch paginated items with custom query
-response = client.item.items_page(
-  limit: 100,
-  query_params: {
-    rules: [{ column_id: "status", compare_value: [5] }]
-  }
-)
+The library provides typed exceptions for different error scenarios:
+
+```ruby
+begin
+  response = client.board.query(args: { ids: [123] })
+rescue Monday::AuthorizationError => e
+  puts "Invalid API token: #{e.message}"
+rescue Monday::InvalidRequestError => e
+  puts "Invalid request: #{e.message}"
+rescue Monday::RateLimitError => e
+  puts "Rate limit exceeded: #{e.message}"
+rescue Monday::Error => e
+  puts "API error: #{e.message}"
+end
 ```
 
+See the [Error Handling Guide](https://sanifhimani.github.io/monday_ruby/guides/advanced/errors) for best practices.
+
+## Available Resources
+
+The client provides access to all monday.com resources:
+
+- **Boards** - `client.board`
+- **Items** - `client.item`
+- **Columns** - `client.column`
+- **Files** - `client.file`
+- **Groups** - `client.group`
+- **Updates** - `client.update`
+- **Subitems** - `client.subitem`
+- **Workspaces** - `client.workspace`
+- **Folders** - `client.folder`
+- **Account** - `client.account`
+- **Activity Logs** - `client.activity_log`
+- **Board Views** - `client.board_view`
+
+For complete API documentation, see the [API Reference](https://sanifhimani.github.io/monday_ruby/reference/client).
+
 ## Development
 
-Run all tests:
+### Running Tests
 
 ```bash
 bundle exec rake spec
 ```
 
-Run linter:
+Tests use [VCR](https://github.com/vcr/vcr) to record HTTP interactions, so you don't need a monday.com API token to run them.
+
+### Linting
 
 ```bash
 bundle exec rake rubocop
 ```
 
+### All Checks
+
+```bash
+bundle exec rake  # Runs both tests and linter
+```
+
 ## Contributing
 
-Bug reports and pull requests are welcome on [GitHub](https://github.com/sanifhimani/monday_ruby). This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/sanifhimani/monday_ruby/blob/main/CODE_OF_CONDUCT.md).
+Bug reports and pull requests are welcome on [GitHub](https://github.com/sanifhimani/monday_ruby).
+
+Please read our [Contributing Guide](CONTRIBUTING.md) for details on:
+- Development setup and testing
+- Documentation guidelines
+- Code style and commit conventions
+
+This project follows the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md).
 
 ## License
 

data/lib/monday/client.rb

@@ -2,6 +2,7 @@
 
 require "uri"
 require "net/http"
+require "net/http/post/multipart"
 require "json"
 
 require_relative "configuration"
@@ -37,6 +38,18 @@ module Monday
       handle_response(Response.new(response))
     end
 
+    def make_file_request(query, variables)
+      response = Request.post_multipart(
+        files_uri,
+        { query: query, variables: variables },
+        request_multipart_headers,
+        open_timeout: @config.open_timeout,
+        read_timeout: @config.read_timeout
+      )
+
+      handle_response(Response.new(response))
+    end
+
     private
 
     def configure(config_args)
@@ -49,6 +62,10 @@ module Monday
       URI(@config.host)
     end
 
+    def files_uri
+      URI(@config.files_host)
+    end
+
     def request_headers
       {
         "Content-Type": "application/json",
@@ -56,6 +73,13 @@ module Monday
       }
     end
 
+    def request_multipart_headers
+      {
+        "Content-Type": "multipart/form-data",
+        Authorization: @config.token
+      }
+    end
+
     def handle_response(response)
       return response if response.success?
 

data/lib/monday/configuration.rb

@@ -7,8 +7,10 @@ module Monday
   #
   # token: used to authenticate the requests
   # host: defaults to https://api.monday.com/v2
+  # files_host: defaults to https://api.monday.com/v2/files
   class Configuration
     DEFAULT_HOST = "https://api.monday.com/v2"
+    DEFAULT_FILES_HOST = "#{DEFAULT_HOST}/file"
     DEFAULT_TOKEN = nil
     DEFAULT_VERSION = "2023-07"
     DEFAULT_OPEN_TIMEOUT = 10
@@ -17,6 +19,7 @@ module Monday
     CONFIGURATION_FIELDS = %i[
       token
       host
+      files_host
       version
       open_timeout
       read_timeout
@@ -29,6 +32,7 @@ module Monday
       raise ArgumentError, "Unknown arguments: #{invalid_keys}" unless invalid_keys.empty?
 
       @host = DEFAULT_HOST
+      @files_host = DEFAULT_FILES_HOST
       @token = DEFAULT_TOKEN
       @version = DEFAULT_VERSION
       @open_timeout = DEFAULT_OPEN_TIMEOUT
@@ -42,6 +46,7 @@ module Monday
     def reset
       @token = DEFAULT_TOKEN
       @host = DEFAULT_HOST
+      @files_host = DEFAULT_FILES_HOST
       @version = DEFAULT_VERSION
       @open_timeout = DEFAULT_OPEN_TIMEOUT
       @read_timeout = DEFAULT_READ_TIMEOUT

data/lib/monday/request.rb

@@ -18,5 +18,20 @@ module Monday
 
       http.request(request)
     end
+
+    def self.post_multipart(uri, body, headers, open_timeout: 10, read_timeout: 30)
+      http = Net::HTTP.new(uri.host, uri.port)
+      http.use_ssl = true
+      http.open_timeout = open_timeout
+      http.read_timeout = read_timeout
+
+      params = {
+        "query" => body[:query],
+        "variables[file]" => body[:variables][:file]
+      }
+
+      request = Net::HTTP::Post::Multipart.new(uri.request_uri, params, headers)
+      http.request(request)
+    end
   end
 end

data/lib/monday/resources/base.rb

@@ -12,6 +12,10 @@ module Monday
 
       protected
 
+      def make_file_request(query, variables)
+        client.make_file_request(query, variables)
+      end
+
       def make_request(query)
         client.make_request(query)
       end

data/lib/monday/resources/file.rb

@@ -0,0 +1,56 @@
+# frozen_string_literal: true
+
+module Monday
+  module Resources
+    # Represents Monday.com's file asset resource.
+    class File < Base
+      DEFAULT_SELECT = %w[id].freeze
+
+      # Adds a file to a file type column for an item.
+      #
+      # Allows customizing the column update using the args option.
+      # Allows customizing the values to retrieve using the select option.
+      # By default, The ID is retrieved.
+      def add_file_to_column(args: {}, select: DEFAULT_SELECT)
+        cloned_args = args.clone
+        variables = { file: cloned_args.delete(:file) }
+        cloned_args.merge!(file: "$file")
+        query = <<~QUERY
+          mutation add_file($file: File!) {
+            add_file_to_column#{Util.format_args(cloned_args)} {#{Util.format_select(select)}}
+          }
+        QUERY
+        make_file_request(query, variables)
+      end
+
+      # Adds a file to an update for an item.
+      #
+      # Allows customizing the update creation using the args option.
+      # Allows customizing the values to retrieve using the select option.
+      # By default, The ID is retrieved.
+      def add_file_to_update(args: {}, select: DEFAULT_SELECT)
+        cloned_args = args.clone
+        variables = { file: cloned_args.delete(:file) }
+        cloned_args.merge!(file: "$file")
+        query = <<~QUERY
+          mutation ($file: File!) {
+            add_file_to_update#{Util.format_args(cloned_args)} {#{Util.format_select(select)}}
+          }
+        QUERY
+        make_file_request(query, variables)
+      end
+
+      # Clear an item's files column. This is a helper method for files
+      # and you could also use the column.change_value to clear the column as well.
+      #
+      # Allows customizing the update creation using the args option.
+      # Allows customizing the values to retrieve using the select option.
+      # By default, ID is retrieved.
+      def clear_file_column(args: {}, select: DEFAULT_SELECT)
+        merged_args = args.merge(value: '{\"clear_all\": true}')
+        query = "mutation { change_column_value#{Util.format_args(merged_args)} {#{Util.format_select(select)}}}"
+        make_request(query)
+      end
+    end
+  end
+end

data/lib/monday/util.rb

@@ -108,6 +108,7 @@ module Monday
 
       def formatted_args_value(value)
         return value if value.is_a?(Symbol)
+        return value if value.to_s.include?("$") # GraphQL query variable
         return value.to_json.to_json if value.is_a?(Hash)
         return value if integer?(value)
         return "[#{value.map { |v| formatted_args_value(v) }.join(", ")}]" if value.is_a?(Array)

data/lib/monday/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Monday
-  VERSION = "1.1.0"
+  VERSION = "1.2.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: monday_ruby
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.2.1
 platform: ruby
 authors:
 - Sanif Himani
@@ -24,7 +24,21 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 0.3.0
-description: A Gem to easily interact with monday.com API using native Ruby
+- !ruby/object:Gem::Dependency
+  name: multipart-post
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.4'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.4'
+description: A Ruby gem for interacting with monday.com's API
 email:
 - sanifhimani92@gmail.com
 - weshays@gmail.com
@@ -32,17 +46,9 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".env"
-- ".rspec"
-- ".rubocop.yml"
-- ".simplecov"
-- ".vscode/settings.json"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- CONTRIBUTING.md
 - LICENSE
 - README.md
-- Rakefile
 - lib/monday/client.rb
 - lib/monday/configuration.rb
 - lib/monday/deprecation.rb
@@ -55,6 +61,7 @@ files:
 - lib/monday/resources/board.rb
 - lib/monday/resources/board_view.rb
 - lib/monday/resources/column.rb
+- lib/monday/resources/file.rb
 - lib/monday/resources/folder.rb
 - lib/monday/resources/group.rb
 - lib/monday/resources/item.rb
@@ -70,8 +77,8 @@ licenses:
 - MIT
 metadata:
   homepage_uri: https://github.com/sanifhimani/monday_ruby
-  documentation_uri: https://monday-ruby.gitbook.io/docs/
-  changelog_uri: https://github.com/sanifhimani/monday_ruby/blob/v1.1.0/CHANGELOG.md
+  documentation_uri: https://sanifhimani.github.io/monday_ruby/
+  changelog_uri: https://github.com/sanifhimani/monday_ruby/blob/v1.2.1/CHANGELOG.md
   rubygems_mfa_required: 'true'
 rdoc_options: []
 require_paths:
@@ -87,7 +94,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.6.9
+rubygems_version: 3.7.2
 specification_version: 4
 summary: Ruby bindings to use the monday.com API
 test_files: []

data/.env

@@ -1 +0,0 @@
-token="eyJhbGciOiJIUzI1NiJ9.eyJ0aWQiOjU3ODczMzkyMiwiYWFpIjoxMSwidWlkIjo5NDg5NDgxMywiaWFkIjoiMjAyNS0xMC0yN1QwMToyMToxMy44NDFaIiwicGVyIjoibWU6d3JpdGUiLCJhY3RpZCI6MzIxODc3OTQsInJnbiI6InVzZTEifQ.SgPS-m2FEMHjitKC0SYTYsiQ8vAHZ7ynjDmMwQInneE"

data/.rspec

@@ -1,2 +0,0 @@
---color
---require spec_helper

data/.rubocop.yml

@@ -1,40 +0,0 @@
-plugins:
-  - rubocop-rake
-  - rubocop-rspec
-
-AllCops:
-  TargetRubyVersion: 2.7
-  NewCops: enable
-  SuggestExtensions: false
-  Exclude:
-    - "spec/support/**/*.rb"
-    - "vendor/**/*"
-
-Style/StringLiterals:
-  Enabled: true
-  EnforcedStyle: double_quotes
-
-Style/StringLiteralsInInterpolation:
-  Enabled: true
-  EnforcedStyle: double_quotes
-
-Layout/LineLength:
-  Max: 120
-
-Metrics/BlockLength:
-  Exclude:
-    - "spec/**/*_spec.rb"
-
-Metrics/MethodLength:
-  Exclude:
-    - "lib/monday/util.rb"
-
-Metrics/ParameterLists:
-  Exclude:
-    - "lib/monday/resources/group.rb"
-
-RSpec/NestedGroups:
-  Max: 5
-
-RSpec/MultipleMemoizedHelpers:
-  Max: 10

data/.simplecov

@@ -1,4 +0,0 @@
-# frozen_string_literal: true
-
-SimpleCov.add_filter "/spec/support/"
-SimpleCov.minimum_coverage 97

data/.vscode/settings.json

@@ -1,4 +0,0 @@
-{
-  "ruby.rubocop.configFilePath": ".rubocop.yml",
-  "files.trimTrailingWhitespace": true
-}

data/CODE_OF_CONDUCT.md

@@ -1,84 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at sanifhimani92@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/CONTRIBUTING.md

@@ -1,86 +0,0 @@
-# Contributing
-
-Thanks for taking the time to contribute!
-
-The following is a set of guidelines for contributing to `monday_ruby`. These are mostly guidelines, not rules. Use your best judgment, and feel to propose changes to this document in a pull request.
-
-## Your first code contribution
-
-Unsure where to begin contributing? You can start by looking through `good first issue` and `help wanted` issues.
-
-### Pull request
-
-Please follow these steps to have your contribution considered:
-
-1. Follow the [pull request template](PULL_REQUEST_TEMPLATE.md).
-2. Follow the [commit guidelines](#commit-message-guidelines).
-3. After you submit your pull request, verify that all the status checks are passing.
-
-## Testing Guidelines
-
-This project uses [VCR](https://github.com/vcr/vcr) to record HTTP interactions for tests. This means you **do not need a Monday.com API token** to run most tests or contribute to the project.
-
-### Running Tests
-
-To run the test suite:
-
-```bash
-bundle exec rake spec
-```
-
-All tests will use pre-recorded VCR cassettes stored in `spec/fixtures/vcr_cassettes/`.
-
-### Working with VCR Cassettes
-
-**For most contributions, you won't need to modify VCR cassettes.** The existing cassettes cover the current API functionality.
-
-#### When You Need to Record New Cassettes
-
-You only need to record new VCR cassettes when:
-- Adding support for a **new API endpoint** that doesn't have existing test coverage
-- Modifying an existing API call that changes the request/response structure
-
-To record new cassettes:
-
-1. Set your Monday.com API token as an environment variable:
-   ```bash
-   export MONDAY_TOKEN="your_token_here"
-   ```
-
-2. Delete the old cassette file (if updating an existing test):
-   ```bash
-   rm spec/fixtures/vcr_cassettes/your_cassette_name.yml
-   ```
-
-3. Run the specific test to generate a new cassette:
-   ```bash
-   bundle exec rspec spec/path/to/your_spec.rb
-   ```
-
-4. **Important:** Before committing, verify the cassette doesn't contain sensitive data:
-   - VCR automatically filters the `Authorization` header
-   - Check for any other sensitive information in the cassette file
-   - Cassettes are committed to the repository
-
-#### Testing New Features Without API Access
-
-If you're adding a new feature but don't have API access to record cassettes:
-1. Write your implementation and tests
-2. Create a pull request noting that cassettes need to be recorded
-3. A maintainer with API access will record the cassettes for you
-
-### Code Quality
-
-Run RuboCop to ensure code style compliance:
-
-```bash
-bundle exec rake rubocop
-```
-
-## Commit message guidelines
-
-* Use present tense ("Add feature" not "Added feature")
-* Use the imperative mood ("Move file to..." not "Moves file to...")
-* Limit the first line to 70 characters or less.
-* Reference issues and pull requests after the first line.
-* Try to follow [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/)

data/Rakefile

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-require "rubocop/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-
-RuboCop::RakeTask.new
-
-task default: %i[spec rubocop]