Repository navigation
Lookup Representers Dynamically #1
Description
Would you consider adding support for automatically extending object with the appropriate representer and releasing this as a gem?
Say something along these lines of:
def call(object, env)
representer_name = "#{object.class}Representer"
if Object.const_definied?(representer_name)
representer_class = Object.const_get()
object.extend(representer_class)
end
Grape::Formatter::Json.call object, env
end
Activity
dblock commentedon Aug 26, 2013
That could work, yes.
johnallen3d commentedon Aug 26, 2013
Cool, I was thinking about it a little more over the weekend and it possible you'd want to have pluralized versions of representers as well. I'll work something up and submit a pull request. Thanks.
[-]Lookup Representers Dynamically?[/-][+]Lookup Representers Dynamically[/+]thisiscab commentedon Jul 22, 2015
Is there any progress on this?
johnallen3d commentedon Jul 22, 2015
Sorry, I've not been working
roarof late and haven't gotten back to this.dblock commentedon Oct 27, 2026
PR #46 documents and verifies Grape’s built-in lookup: assign a representer module or decorator to
Product::Entity, then callpresent productwithoutwith:. Decorator classes also support API-localrepresent Product, with: ProductRepresentermappings without modifying the model. An explicitwith:overrides inference.This avoids global class-name guessing and singular/plural ambiguity. It does not silently mutate arbitrary endpoint return values; call
presentto request inference. Request regressions cover both module/decorator inference, overrides, and API-local mapping.Posted by Copilot, an AI, on behalf of @dblock.