monday_ruby 1.2.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 65df3dcbdada1d02fb3573b444015cb6b566d6b77cc1d63d103d6b5e7803f65b
-  data.tar.gz: 319fd612684e644dc0235c0010ece6890214f844d5b48f3f9238319ff77e70c5
+  metadata.gz: 3837300eeee4b5c5fc64a1c69eccc897cbbf57dc05acfaba3163bd67d1d1beb8
+  data.tar.gz: c0164784b3ec5b9780e735082e47f5f6381d8b115a11310addb707c046b84f0d
 SHA512:
-  metadata.gz: bc4f34d8de144d95b4fe9cc78ea9801614389c4be7aaf72ba29186d6447d14200c95a3814ed5d8a3106045142b81f10b38fe7045ca8fcb5549153acf59b63c95
-  data.tar.gz: e5c15771ea6c5ec86e2b12508860c1927d67017b223b40c51b921ee28912a691aaa2750f39ef08ec6d9efec091a5d3fdaf07393e920e8b907b34659d72372a4a
+  metadata.gz: fb6897aa4cb9810db87e09f0d70a9614d01cc5685c1cd5992780c0838e6f5a84444d430ad20454dd1a144d897a037fb84dc40b2cc9fb88289222f3a5cad7860a
+  data.tar.gz: 5642bf287741d7d3464142e5a4c78ce8d9da29be8ded5f9849820e6b6112258e8f3a8273618388c656649b89ba9d426106b91595e9f188c8ea1fb9d89c54f895

data/CHANGELOG.md

@@ -1,3 +1,13 @@
+## 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

data/lib/monday/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Monday
-  VERSION = "1.2.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.2.0
+  version: 1.2.1
 platform: ruby
 authors:
 - Sanif Himani
@@ -38,7 +38,7 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '2.4'
-description: A Gem to easily interact with monday.com API using native Ruby
+description: A Ruby gem for interacting with monday.com's API
 email:
 - sanifhimani92@gmail.com
 - weshays@gmail.com
@@ -46,85 +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
-- docs/.vitepress/config.mjs
-- docs/.vitepress/theme/index.js
-- docs/.vitepress/theme/style.css
-- docs/README.md
-- docs/explanation/architecture.md
-- docs/explanation/best-practices/errors.md
-- docs/explanation/best-practices/performance.md
-- docs/explanation/best-practices/rate-limiting.md
-- docs/explanation/best-practices/testing.md
-- docs/explanation/column-values.md
-- docs/explanation/design.md
-- docs/explanation/graphql.md
-- docs/explanation/migration/v1.md
-- docs/explanation/pagination.md
-- docs/guides/advanced/batch.md
-- docs/guides/advanced/complex-queries.md
-- docs/guides/advanced/errors.md
-- docs/guides/advanced/pagination.md
-- docs/guides/advanced/rate-limiting.md
-- docs/guides/authentication.md
-- docs/guides/boards/create.md
-- docs/guides/boards/delete.md
-- docs/guides/boards/duplicate.md
-- docs/guides/boards/query.md
-- docs/guides/boards/update.md
-- docs/guides/columns/create.md
-- docs/guides/columns/metadata.md
-- docs/guides/columns/query.md
-- docs/guides/columns/update-multiple.md
-- docs/guides/columns/update-values.md
-- docs/guides/files/add-to-column.md
-- docs/guides/files/add-to-update.md
-- docs/guides/files/clear-column.md
-- docs/guides/first-request.md
-- docs/guides/folders/manage.md
-- docs/guides/groups/items.md
-- docs/guides/groups/manage.md
-- docs/guides/installation.md
-- docs/guides/items/create.md
-- docs/guides/items/delete.md
-- docs/guides/items/query.md
-- docs/guides/items/subitems.md
-- docs/guides/items/update.md
-- docs/guides/updates/manage.md
-- docs/guides/use-cases/dashboard.md
-- docs/guides/use-cases/import.md
-- docs/guides/use-cases/task-management.md
-- docs/guides/workspaces/manage.md
-- docs/index.md
-- docs/package-lock.json
-- docs/package.json
-- docs/reference/client.md
-- docs/reference/configuration.md
-- docs/reference/errors.md
-- docs/reference/resources/account.md
-- docs/reference/resources/activity-log.md
-- docs/reference/resources/board-view.md
-- docs/reference/resources/board.md
-- docs/reference/resources/column.md
-- docs/reference/resources/file.md
-- docs/reference/resources/folder.md
-- docs/reference/resources/group.md
-- docs/reference/resources/item.md
-- docs/reference/resources/subitem.md
-- docs/reference/resources/update.md
-- docs/reference/resources/workspace.md
-- docs/reference/response.md
-- docs/tutorial/first-integration.md
 - lib/monday/client.rb
 - lib/monday/configuration.rb
 - lib/monday/deprecation.rb
@@ -154,7 +78,7 @@ licenses:
 metadata:
   homepage_uri: https://github.com/sanifhimani/monday_ruby
   documentation_uri: https://sanifhimani.github.io/monday_ruby/
-  changelog_uri: https://github.com/sanifhimani/monday_ruby/blob/v1.2.0/CHANGELOG.md
+  changelog_uri: https://github.com/sanifhimani/monday_ruby/blob/v1.2.1/CHANGELOG.md
   rubygems_mfa_required: 'true'
 rdoc_options: []
 require_paths:

data/.env

@@ -1 +0,0 @@
-token="[REPLACE_TOKEN]"

data/.rspec

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

data/.rubocop.yml

@@ -1,41 +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/configuration.rb"
-    - "lib/monday/util.rb"
-
-Metrics/ParameterLists:
-  Exclude:
-    - "lib/monday/resources/group.rb"
-
-RSpec/NestedGroups:
-  Max: 5
-
-RSpec/MultipleMemoizedHelpers:
-  Max: 11

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,190 +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
-```
-
-## Documentation
-
-The project uses [VitePress](https://vitepress.dev/) to generate documentation from Markdown files. The documentation site is hosted at [https://sanifhimani.github.io/monday_ruby/](https://sanifhimani.github.io/monday_ruby/).
-
-### When to Update Documentation
-
-Update documentation when you:
-- Add a new resource or method to the public API
-- Change the behavior of existing methods
-- Add new features or configuration options
-- Fix bugs that affect documented behavior
-
-### Documentation Structure
-
-Documentation follows the [Diataxis framework](https://diataxis.fr):
-
-- **Tutorial** (`docs/tutorial/`) - Learning-oriented, gets users started
-- **How-to Guides** (`docs/guides/`) - Task-oriented, solves specific problems
-- **Reference** (`docs/reference/`) - Information-oriented, describes the API
-- **Explanation** (`docs/explanation/`) - Understanding-oriented, explains concepts
-
-### Adding/Updating Documentation
-
-Documentation files are located in the `docs/` directory:
-
-```
-docs/
-├── .vitepress/
-│   └── config.mjs          # Navigation and site configuration
-├── guides/                 # How-to guides
-│   ├── boards/
-│   ├── items/
-│   ├── columns/
-│   └── advanced/
-├── reference/              # API reference
-│   ├── resources/
-│   └── client.md
-├── explanation/            # Conceptual documentation
-└── tutorial/               # Getting started tutorial
-```
-
-#### Steps to Update Documentation:
-
-1. **Find or create the appropriate file** based on what you're documenting
-2. **Follow the existing format** - look at similar documentation files for examples
-3. **Test your code examples** - all examples should be runnable and accurate
-4. **Update navigation** if adding new pages - edit `docs/.vitepress/config.mjs`
-5. **Build locally** to preview changes:
-
-```bash
-cd docs
-npm install  # First time only
-npm run dev  # Start local dev server
-```
-
-Visit `http://localhost:5173/monday_ruby/` to preview your changes.
-
-6. **Check for broken links** before submitting:
-
-```bash
-cd docs
-npm run build  # Build will fail if there are dead links
-```
-
-#### Documentation Guidelines:
-
-- **Code examples must be accurate** - verify against VCR test fixtures or real API
-- **Include practical examples** - show real-world usage, not just syntax
-- **Be consistent** - follow the style and tone of existing documentation
-- **No emojis** - maintain professional tone in documentation
-- **Link related pages** - help users discover relevant documentation
-- **Keep examples self-contained** - users should be able to copy-paste and run
-
-#### Example Documentation Pattern:
-
-```markdown
-# Resource Name
-
-Brief description of what this resource does.
-
-## Methods
-
-### method_name
-
-Description of what the method does.
-
-\`\`\`ruby
-# Example code that actually works
-client = Monday::Client.new(token: ENV["MONDAY_TOKEN"])
-response = client.resource.method_name(args: {})
-\`\`\`
-
-**Parameters:**
-- List parameters and their types
-
-**Returns:** Description of return value
-
-**See:** Link to monday.com API docs
-```
-
-### Deploying Documentation
-
-Documentation is automatically deployed via GitHub Actions when changes are merged to the `main` branch. You don't need to manually deploy.
-
-## 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]