passwords tokens apikeys that are fully numeric causing yml validation issues

[bullmoose20]

we need to address a password that is 100% numeric as the yaml validation thinks it is a number instead of a string. (Is this a schema.json fix or a wizard fix? I am not sure.

Originally posted by @bullmoose20 in #3 (comment)

[bullmoose20]

I put in a fake numeric only gotify api key forced the validate to true so that i could jumpto the final validation to share the error.

I suspect that the issue lies with the actual json schema?

[bullmoose20]

Or maybe we need to force fields being written as strings when they are all numeric?

[chazlarson]

Yes, the value expects a string and that's a number.

[bullmoose20]

So the real question I think is whether this is a json-schema issue or a QuickStart issue.

Like will Kometa accept an all numeric username or password or secret in general or does it need to have single quotes around it?