David Halls
David Halls
It looks like only `matroska/lib/schema` is used. node-ebml has a schema.js which could be used instead?
Also worth investigating where `matroska/lib/schema` originally came from in case it was taken from a different project originally.
node-matroska was originally forked from node-ebml.
I've made https://github.com/davedoesdev/matroska-schema under MIT licence which might be useful here. It automatically generates schema.js from the Matroska EBML files. Published on npm as `matroska-schema` - just `require` it and...
I can help out, can't promise super quick turnaround though.
+1 this would be great to enable many isolated networks for multi-tenancy
I don't think `TrieAscoltatore` cares about duplicates does it?
I tried an approach which removed the `description` fields and then did a deep comparison. That does work but resulted in referencing interfaces that may be the same in structure...
> I think you can use a shallow comparison, right? Per (1) and (2) above, we should maintain referential identity, even after de-referencing, and if we don't, that should be...
I fixed it with #318 for internal refs to `#/definitions/` only. It has a new option `resolve` which you have to set to `false` to let the `$ref` be handled...