Move Paperclip Adapter into extension
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Paperclip is deprecated and unsupported, with ActiveStorage being the recommended substitute.
Although some shops won't have issues in the short term, they will eventually face problems when updating the stack since Paperclip does not support newer versions of Ruby and Rails.
Our major concern is providing users with a solid migration path; however, we cannot see a zero-effort migration.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading Solidus issue #5033, which this roadmap item links for context on Paperclip and migration concerns. Identify the adapter's current location and extension structure before scoping the move; done should mean the Paperclip adapter is isolated in an extension with a viable migration path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100