Skip to content

Add a "class category" level between global and per-type config overrides #10

@cowtowncoder

Description

@cowtowncoder

Currently granularity of config overrides is coarse: there is the global default for everything, and then overrides for exact (base) type. But there are many cases where one would want to apply settings to category of types, such as:

  • All enums
  • Collections
  • Anything serialized as JSON Array (Collections, arrays)
  • Anything structured (serialized as JSON Arrays, Objects)
  • Scalars
  • Reference types (Optional, AtomicReference)

If so, we would get 3 levels:

  1. Global defaults
  2. Type categories (possibly limited hierarchy, 2-3 levels at most)
  3. Types

It should be possible to just create an enumeration, with tree structure linking levels, to automatically handle level (2). A little bit goes a long way here, as well, no need for dozens of categories or attempts at overlapping (not neatly contained) categories.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions