Skip to content

Go: Bad codegen when using colliding method + type APIs #89

@gotwarlost

Description

@gotwarlost

Use case:

I had a resource resource Foo GET /bar/baz. I also want resource Foo Get /something/else (for backwards compatibility).

To do that I name one of the resources different from the generated name. Problem is that schema stills has 2 variables named mGetFoo and does not compile. The member variables in the schema should be named using the resource name if available and not always use the generated name.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions