make different gems for models and adapters

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
backend

Research direction

The issue body only says “subj” and names no files, tests, or entry points. Start by inspecting the repository’s gem structure and packaging configuration to determine how models and adapters are organized; done would mean they can be released as different gems, but the required design and boundaries are not specified.

Written by the indexing model from the issue text.

Description

subj

Dominant language
Ruby
Stars
27
Forks
12
PR merge metrics
No merged PRs in 30d

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.

More from umbrellio/table_sync

All issues in umbrellio/table_sync

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.