Add find_or_create_by and find_or_create_by! with block support

[Copilot]

Implements ActiveRecord-style find_or_create_by and find_or_create_by! for finding existing records or creating new ones, with full support for Rails-style block yielding.

Changes

• Base class methods: Added create(attributes, &block) and create!(attributes, &block) for creating and saving records. create! raises RecordInvalid on validation failure. Both methods accept an optional block that gets yielded to the new record before saving.
• Scoping module: Added find_or_create_by(conditions, &block) and find_or_create_by!(conditions, &block). The bang version raises on validation errors. Both methods accept an optional block that only executes when creating (not when finding existing records).
• Version: Bumped to 0.3.0 for new backward-compatible features.

Usage

# Returns existing record or creates new one
user = User.find_or_create_by(email: "alice@example.com")

# Raises RecordInvalid if creation fails validation
user = User.find_or_create_by!(email: "alice@example.com", name: "Alice")

# Block yielding (Rails-style) - only runs when creating new record
user = User.find_or_create_by(email: "alice@example.com") do |u|
  u.first_name = "Alice"
  u.last_name = "Smith"
end

Block Yielding

The block parameter works exactly like Rails' ActiveRecord:

• Block receives the new record before it's saved
• Block only executes if the record is being created (not found)
• You can set additional attributes or run custom logic in the block

Implementation notes

Uses traditional find-then-create approach (2 API calls) rather than Airtable's performUpsert. Upsert would update existing records, which violates find_or_create_by semantics. Field mappings work correctly in both find and create operations.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>we need #find_or_create_by{,!}!</issue_title>
<issue_description></issue_description>

<agent_instructions>make it happen, cap'n</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes we need #find_or_create_by{,!}! #1

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[24c02]

@copilot what about yielding like rails?

[Copilot]

@copilot what about yielding like rails?

Added block yielding support in commit 68918bd. Both find_or_create_by and find_or_create_by! now accept a block that gets yielded to the new record only when creating (not when finding existing records). Version bumped to 0.3.0.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.airtable.com
  • Triggering command: /home/REDACTED/.local/share/gem/ruby/3.2.0/bin/rspec rspec --format documentation (dns block)
  • Triggering command: /home/REDACTED/.local/share/gem/ruby/3.2.0/bin/rspec rspec --format progress (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)