Repository navigation
Split addedTypes/overridingTypes/removedTypes by topics #2053
Description
I don't think monolithic files help much. Smaller topic-by-topic files would help understanding why they exist, e.g. Streams customization can go into "streams" topic.
Given this will add new files, I'd like to try KDL for new ones than having to use JSON.
Activity
Bashamega commentedon Jun 30, 2025
Hello Kagami Sascha Rosylight (@saschanaz)
KDL seems cool. Can I try to migrate it, or this is still for discussion?
saschanaz commentedon Jun 30, 2025
I was planning to do this only when we have to add a new set up customization, but given we already have PRs like #2050 maybe we should try this before that, so that we can tell others to use it.
So yes, 👍🏻 from me
saschanaz commentedon Jun 30, 2025
Why KDL - it's mature enough (has been there for years), recently embraced by bikeshed (the web spec generator that over half of the specs depend on), has types so that we can do this:
(Our input data was migrated from XML which is why it's still XML-ish with
.properties.property, I think KDL fits better for that.