PLEASE deprecate this repo and link to Airrecord

[arturadib]

As already reported in some issues, some of the core functionalities of this repo are broken (e.g. updates, deletes), so please link to a repo that's actually being maintained and isn't broken – for example https://github.com/sirupsen/airrecord.

I hope this will prevent others from investing time and effort in a dead-end like we did :)

Thank you!

cc @syrnick

[nekapoor]

Thanks @arturadib. I've been banging my head trying to figure out why the updates aren't working. Pretty ridiculous.

[syrnick]

The plan is to look for maintainers and simplify this asap. It will be a minimalistic API client, but it should definitely be a working one. The current API makes certain things impossible (e.g. not sending back formulas), so the API will change.

https://github.com/sirupsen/airrecord is great and we'll definitely improve it's visibility. It does have issues(e.g. incorrect escaping of table names v.s. 3cc21ea) and provides certain ruby magic (e.g. column_mappings) that's very helpful and works most of the times, but is not guaranteed to work always.

[sirupsen]

@syrnick Airrecord uses the Faraday escaping. Is that incorrect? It's worked for me in the cases I've tried.

I agree that column mappings are problematic. However, doesn't this library basically do the same thing for ergonomic reasons? I'm fairly sure that's how I was inspired to do it. In what cases has it not worked for you?

Airrecord also has a simple API mode that's very similar to this library. You don't need to use the ActiveModel-like API.

[Meekohi]

@syrnick -- Seems like "ASAP" came and went, please consider deprecating this repository until you find a maintainer.

[sirupsen]

FWIW the confusing the "ruby magic" symbol API has been deprecated (sirupsen/airrecord#33) and will be fully removed in 1.0.0 which is due for release soon with a bunch of other improvements (cc @chrisfrank).

As for the table escaping, I've had zero issues with Airrecord. Do you have a table name that's problematic?

[chrisfrank]

Today's release of Airrecord 1.0 removes the magic symbol API, throttles requests by default to respect Airtable's rate limit, and encodes URLs in compliance with the spec @syrnick linked to.

I share @syrnick's wish for an officially-supported, minimalistic ruby client, but respectfully I think "minimalistic" is a better description of Airrecord than airtable-ruby at this point. ActiveSupport is an enormous dependency that changes the behavior of Ruby's core classes, and it makes airtable-ruby a costly choice in non-Rails contexts.

Also, to echo @sirupsen above, although Airrecord makes it possible to write ORM-style code, it's also perfectly happy being a small, functional-style API client, and the forthcoming 1.1 release will augment the functional API to more closely mimic the official Node client.