I should clarify that this is not an SSWG requirement, it's my opinion. The only thing the incubation process process requires regarding dependencies is that their licenses are listed in the proposal.
I agree that being DRY and not reinventing the wheel everywhere is very important. But I think being overly DRY is a problem as well. NPM's ecosystem is the obvious example here with packages like is_integer that are literally one line.
In order to use these 3 methods
node_modulesneeds 1826 files. And that’s just 4 of mentioned 976 installed packages.
From: https://hackernoon.com/whats-really-wrong-with-node-modules-and-why-this-is-your-fault-8ac9fa893823
NPM's package bloat has caused big technical and security problems.
That being said, I don't know where AnyCodable, OrderedDictionary, or Poly fit on this spectrum. Are they complex enough that they merit their own package and we should be re-using them? Does not re-using them create real usability problems for consumers of OpenAPIKit? Are we only using a very small subset that would make more sense for direct inclusion? Does adding this dependency create unnecessary bloat?
Those are great questions and worth discussing with evidence in this proposal. My initial argument was simply "I don't know" and to err on the side of being conservative here. That is not a requirement of the SSWG or even what the other SSWG member's opinions may be.