multiple error messages when used as params
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 40/100
Research direction
Reproduce the example using Grape::Entity documentation as the schema for requires :all, using: Entity.documentation. Start by tracing how the car documentation becomes parameter validation and how missing and invalid-value errors are collected. Done means the example reports only the invalid-value message when car is present with an unsupported value, while preserving the intended behavior for missing values.
Written by the indexing model from the issue text.
Description
class Entity < Grape::Entity
expose :car, documentation: { type: String, values: ["foo", "bar"] }
end
And then use it as validation with
params do
requires :all, using: Entity.documentation
end
"car is missing, car does not have a valid value"
Anyway, for it to just have the second one of the error messages? If I don't make it required then it does not show up at all.
- Dominant language
- Ruby
- Stars
- 729
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Getting set up
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.
More from ruby-grape/grape-entity
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ruby-grape/grape-entity#386 · 7 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ruby-grape/grape-entity#382 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ruby-grape/grape-entity#380 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ruby-grape/grape-entity#373 · 2 comments ·
-
Truncate FormatterOpen
Difficulty 1/5 1-3 hours Newbie friendliness 45/100
ruby-grape/grape-entity#372 ·
All issues in ruby-grape/grape-entity
Similar issues
-
バグ
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
IBM/ai-security-baseline#25 ·
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day