JSONAPI-Resources / JSONAPI-Resources/jsonapi-resources

Official Sequel (and other ORMs) Support Thread

Open
#1,006 10 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
2.3k
Forks
546
PR merge metrics
No merged PRs in 30d

Description

I'm working on the Sequel adapter for this library. With it, I will do the following:

  • Take the library to actually being fully decoupled from ActiveRecord, just like Rails (if you want to use Rails without having ActiveRecord in your top-level namespace, you can). It would be nice to have this also be a characteristic of this library.
  • Support Sequel - be able to run all the specs with all the original models but interfacing with Sequel. This can be done by changing the "ORM" environment variable when running specs.

The library seems to be written with the intent for it to be decoupled from the orm used by the user but doesn't go all the way. With this, the orm specific logic will be housed in one place.

Any additional thoughts or opposition to the idea?

Any other Sequel or other ORM users out there who want to use this library? Please like this so I know how many of you are out there...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the library's ORM environment handling and the ActiveRecord-specific logic described in this thread. Run the existing specs with the current ORM setting, then determine the scope needed for Sequel support and ORM decoupling. Done means the specs pass against Sequel and the ORM-specific logic is isolated as proposed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
backend, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.