Generates bad enum constant if enum value is all punctuation

[mgabeler-lee-6rs]

Given a field like:

				"logic": {
					"type": "string",
					"enum": ["<", "<=", "==", "!=", ">", ">="]
				},

The generated code looks something like:

const Logic Logic = "=="
const Logic Logic = "!="
const Logic Logic = ">"
const Logic Logic = "<"
const Logic Logic = ">="
const Logic Logic = "<="

which is obviously invalid.

It looks like Caser.Identifierize needs handling for the case when the initially computed identifier is the same as the type name, and schemaGenerator.makeEnumType might also need some handling if multiple enum values map to the same constant name, to append _1,_2 etc or some other disambiguator.

[bbrcan]

I've got the same issue. I've got an enum for timezones, with values copied from tzdata. I end up with this:

const TimezoneEtcGMT0 Timezone = "Etc/GMT0"
const TimezoneEtcGMT0 Timezone = "Etc/GMT+0"
const TimezoneEtcGMT0 Timezone = "Etc/GMT-0"
const TimezoneEtcGMT1 Timezone = "Etc/GMT+1"
const TimezoneEtcGMT1 Timezone = "Etc/GMT-1"
const TimezoneEtcGMT10 Timezone = "Etc/GMT+10"
const TimezoneEtcGMT10 Timezone = "Etc/GMT-10"
const TimezoneEtcGMT11 Timezone = "Etc/GMT+11"
const TimezoneEtcGMT11 Timezone = "Etc/GMT-11"
const TimezoneEtcGMT12 Timezone = "Etc/GMT-12"
const TimezoneEtcGMT12 Timezone = "Etc/GMT+12"

Which as you can see generate duplicate names, resulting in errors like TimezoneEtcGMT0 redeclared in this block

In my case, this would be resolved by some substitutions:

• + → Plus
• - → Minus

But then at the same time, I don't really want to substitute a / with ForwardSlash.

My current workaround is after running go-jsonschema I just use sed to remove the const declarations altogether as I don't need them.