Tony

The above ideas can actually all coexist and might make for a nice DX where, at a glance, you have insight into which keys of the filter object originate from...

I'd suggest raising a PR of this pointed at an ESLint target branch, as ESLint won't pass the pipeline until those instances of `any` are removed.

Yeah that's what I was thinking: ```ts // this one feels real good to me but is a bit SQL-biased in terminology { path: 'content/markdown/posts', collection: 'Post', primaryKey: 'meta.id', refs:...

Actually yeah I think I like `primaryKey` the most since it's ubiquitous in relational data

Apologies for the late reply to this issue - would you be able to provide a sample YAML file that the transformation is throwing this error on?

@brandon-welsch if you switch the file to: ```yaml --- test: "value" ``` do you still see this issue?

@lukaszarpak could you provide a minimal reproduction repo? I have not yet been able to reproduce this issue

Apologies for the months-late reply - this is an interesting concept that we're open to supporting! I would love to know more details on the most desirable combination mechanism and...

Found these resources useful: - https://developer.chrome.com/blog/sourcemaps/#the-anatomy-of-a-source-map - https://github.com/tctree333/js-yaml-source-map - Note, this does not generate sourcemaps in the expected browser convention but provides a great resource on generating a sourcemap as...

I think the sourcemap would be useful for mapping back through the conversion to which line in the original YAML file is incorrect, however the YAML processor essentially does that...