kopper @w.on-t.work · 22/08/2026had another idea. a bit worried about this because it breaks the pre-existing conventions of one thing not serving two purposes but in this case i really think the convenience benefits are worth it 131
kopper @w.on-t.work · 22/08/2026just realized this places the parameter's metadata on the parent route instead of the children's. it's workable (filter the path parameters to only ones that have a corresponding path part) but i really wish there was a better way to do that 110
kopper @w.on-t.work · 22/08/2026i mean,,, i don't strictly need a "param metadata", that's more or less legacy from when param was a separate thing from the route itself. you have access to the parts making up the whole route in metadata, which are scoped correctly 140
