DanCardin

I can't repro the CI test failures locally (and in fact the CI is running the tests twice, so it's succeeding on the first go in CI even...), so that's...

I can agree to your general statement because `ruff-lsp` exposes an "organize imports" and a "fix all issues" action **always**. And I essentially always want "fix all issues". But my...

Idk if you'd consider it part of this more general feature, but not counting stuff like `if TYPE_CHECKING:` blocks is also a blocker for me. I **do** have that as...

The above PR represents a very bruteforce approach, namely in that it's not clear to me how to arrive at parity to the old, seeming much simpler, mechanism without first...

we recently found ourselves wanting this at $job. i may look into a relatively simple initial implementation somewhat soon. My personal plan/preference would be for fakesnow to simply internally track...

my personal usecase requires a storage integration/s3, but presumably my implementing that will be easier if there was already general support against a staged file://

In fact, it's significantly more difficult and ambiguous when allowing `Annotated[int, Arg()] | Annotated[str, Arg()]`. Namely, because parsing of values into their resultant types happens **after** parsing has completed, by...

I dont know if relevant, but I used `FROM load_aws_credentials(redact_secret=false)` to steal the keys from the loaded secret and ran `aws sts get-caller-identity` against them. This yielded `"Arn": "arn:aws:sts:::assumed-role/...-k8s-worker-node-role/..."`. Whereas...

I'd already realized that the current interface implies too much commonality among dialects. As such my PR begins to remove the concept of materialized views from the generic base version....

I'd appreciate it if you could test the PR out ahead of my merging it, to make sure it does what you're anticipating it do.