- Issue created by @wim leers
- πΊπΈUnited States phenaproxima Massachusetts
Wim Leers β credited phenaproxima β .
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
@phenaproxima proposed:
'block_count' is an unknown key because plugin is aggregator_feed_block (see config schema type block.settings.* β no more specific type was found).
I propose:
'block_count' is an unknown key because plugin is aggregator_feed_block (see config schema type block.settings.* β this is a fallback type, no more specific type matches).
- πΊπΈUnited States phenaproxima Massachusetts
Sure, I like your wording too. I would maybe alter it ever so slightly:
'block_count' is an unknown key because plugin is aggregator_feed_block (see config schema type block.settings.* β this is a fallback type, no more specific type was found).
I would not use the word "matches" because it's unclear if we're talking about the verb, "to match", or a noun, like "there is such a thing as specific type matches and there aren't any". (I know these mean the same thing, but I think it's worth removing any trace of ambiguity from the wording.)
- πΊπΈUnited States phenaproxima Massachusetts
Nice idea, @borisson_. Telling developers what they can do about an error can't hurt!
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
#5: That's not accurate. It's fine to not have a detailed config schema type. For example, a filter or a block may have no settings at all, in which case the fallback name
block.settings.*
orfilter.settings.*
is entirely appropriate β no additional config schema type needed! - Assigned to wim leers
- Status changed to Active
about 1 year ago 8:08am 27 December 2023 - π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
π Refine ValidKeysConstraintValidator's messages: use #3401883's new Mapping infrastructure Needs review landed!
- Issue was unassigned.
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
Doesn't need to be me doing this actually :)