Why you used :klass name for check respond?
Open
Nobody has claimed this yet.
bug?
- Dominant language
- Ruby
- Stars
- 10k
- Forks
- 1.2k
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 92
Description
I've relation belongs_to :klass within my class.
And code https://github.com/intridea/grape/blob/master/lib/grape/dsl/inside_route.rb#L254 is fallen, because here we have checking if object is respond to klass.
Could you provide use cases for checking respond_to :klass ?
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 in lib/grape/dsl/inside_route.rb around line 254 and inspect how the respond_to check handles an application defining a belongs_to :klass relation. Reproduce the reported failure and review the surrounding route-handling behavior. Done means establishing whether the collision is an unintended bug and documenting or resolving the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100