Maximilian Roos

> * Allow relative paths, to enable the current behaviour. Relative paths are "capped" to traverse only up to `CARGO_MANIFEST_DIR` to prevent placing files outside of the Rust workspace. >...

> It would however be nice if you could bring me up to speed on the current situation. I haven't looked into custom extensions yet. This is a field on...

Is there a minimal example? I see the SQL in the linked issue but can't see the PRQL.

OK, thanks. So it sounds the minimal example: ```elm prql target:sql.sqlite from foo derive x ~= 'bar$' ``` ...shouldn't generate... ```sql SELECT *, x REGEXP 'bar$' FROM foo -- Generated...

Unfortunately those aren't in the interface at the moment. The default `adjust` is `True`. I hadn't found any cases for `ignore_na=True`, though maybe this is one? If the missing values...

Yes that definitely makes sense. I was wondering what the underlying use case was, such that you want to ignore the missing values in your calc? I think this is...

Not the maintainer but IIUC `force_pass` determines whether the test panics immediately or not: https://github.com/mitsuhiko/insta/blob/acb1ce59cb1ddab7c7f240eb352694ff5df1b8ba/insta/src/runtime.rs#L527-L536 (the names do seem confusing and possible we could consolidate these settings here — do...

Cool! Possible these can be consolidated — I _think_ `force_pass` is used by `cargo-insta` to indicate to the `insta` tests that `cargo-insta` will handle the failures at the end, and...

How feasible would it be to allow defining options in a `conftest.py` within the tests path? That would mean we didn't need to put the `conftest.py` file in the root,...

(Yes, I thought I asked something similar a while ago around `pooch` but can't find it) Ideally we would allow `{name="xarray", default-features=false}` for the minority of users that want the...