Various improvements to rule option lists

[bmish]

E.g.

• Support more fields from JSONSchema
• Handle different kinds/nesting of JSONSchemas besides just plain objects
• Can we accommodate other sources of rule options defaults as discussed in feat: Support for meta.defaultOptions on rules eslint/rfcs#113?
• Show a useful value if someone uses a default like Number.MAX_VALUE instead of 1.7976931348623157e+308
• Extract this logic into a separate library

Improvements so far:

• Indicate type of array for array options in rule option lists #496
• Handle when an option could have multiple types in rule option lists #498
• Better display of rule option default for array option #503

Follow-up to:

• Support auto-generated rule options lists #481

[TheSonOfThomp]

Unless I'm missing something, options defined as type: "string" will also not show up in the docs automatically

[bmish]

@TheSonOfThomp I assume you mean a rule like quotes that is configured with a string value instead of an object: quotes: ["error", "double"]. Yes, we haven't supported that type of rule config yet.

[TheSonOfThomp]

Exactly, yeah. Something defined in the schema as:

schema: [{
  type: "string",
  description: "..."
}]

I'm able to use an object property for now (which may be a better api for my case)

[bmish]

An object API for rules is almost always a better choice as it allows you to add additional options later (much more future-proof). However, it would still be good for us to support the basic string scenario.