ruby-grape / ruby-grape/grape

Extract validations module to a gem

Open
#964 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Ruby
Stars
10k
Forks
1.2k
Avg merge
14h 38m
Merged PRs (30d)
92

Description

In our project we are using successfully grape without validations. The idea is that you have to validate data in a controller layer (form objects or service objects, doesn't matter) and often we have to write rather complex validations anyway. So it doesn't make any sense to validate the got params twice: in the controller layer and in grape level. So I would suggest to extract the validations to a separate optional gem. What dot you think about this?

Contributor guide

Open the contributing guide

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

The issue does not name files, tests, or entry points. Begin by locating the current validation implementation and reviewing the gem structure and dependency boundaries; done means the validation functionality is cleanly separated into an optional gem with an agreed migration path and coverage for existing behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.