Commit graph

5 commits

Author SHA1 Message Date
2fdba4f217
content, change overrides to union from object
Technically union is more apt here, because the object will have an
associated schema, it's just unclear what the type for that schema
should be. For instance, does tvdb own the schema under their own
domain? or is it more apt for my.spoor to control it? Going forward I
will use an appropriate tld from the owner of the schema. This should
allow adoption from external providers later if lexicon does take off.
2025-05-14 17:00:40 -07:00
3ba7c0987a
Meta, add examples for lexicons 2025-05-08 16:31:30 -07:00
d6637bb96d
content, add type to tvdbv4 2025-05-08 16:31:06 -07:00
42f93c610a
Content, collapse source/queryable, add tvdbv4
Removed the source field, and made queryable be a union where the type
will reveal how to query, and the data to query will be contained
within. (This is much smarter)...

Changed overrides to be a simple empty object (which should be fine in
the spec). This reflects what it should actually be.

Finally explicitly added the tvdb api v4 option.
2025-05-08 15:25:20 -07:00
a18e052a77
Meta, remove lexicons/ folder prefix 2025-05-08 15:02:55 -07:00