Hi folks! I'm running into an issue with generated go-server code, and to be completely honest, I'm not 100% sure this is the fix, I just know it solves my problem, but I cannot really judge which unintended side effects it may have.

When I have an OpenAPI spec that has parameters typed as enums:

{
  "name": "entityType",
  "in": "query",
  "description": "Entity type",
  "schema": {
    "type": "string",
    "enum": [
      "OPTION_1",
      "OPTION_2",
      "OPTION_3"
    ]
  }
}

This currently generates the following code:

entityTypeParam, err = NewstringFromValue(query.Get("entityType"))

But that's a function that does not exist. I'm not sure this part of the template is really supposed to apply to enum values. I just know that overriding this template locally which this change, my generated code compiles. If this change makes sense, there are still different instances of isEnumOrRef in this template, and I'm also not sure if the same change should be applied there.

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh ./bin/configs/*.yaml
  ./bin/utils/export_docs_generators.sh
  

Unfortunately I cannot install Java on my machine, so this is not an option, sorry.

• File the PR against the correct branch: master (upcoming 7.1.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request. /cc @lwj5