Joe Taber

@rikkiprince that's what would make a SAS-like token the best possible solution. The key point is that each client gets a *unique* short-duration instrumentation key, that's all you can control,...

Thanks for responding to my overly detailed issue description in kind! 😅 I mostly agree with your thoughts on the options I presented, and acquiesce that 5 is probably the...

Both of your examples trying to put environment-specific overrides underneath the main object declaration rubs me the wrong way, though I'm not sure I can articulate why. Maybe because it...

After thinking about rule No 5, I'm not sure if this is the right way to solve dependency problems. E.g. how would a service consume from a 'shared' topic defined...

Some time ago I tried (and failed) to make a NonNull *Attribute*. The problem is that you trust your resolver to return nonnull data, but the only way to communicate...

An option that I would like is quick export to a temp file that is cleaned up later. Maybe labeled "Present with HTML" / "Present with PDF" / ...

Perhaps add a `Dir` Op constant?

I think it would be helpful if `depends` added an option to export the relevant data from all parsed `project.assets.json` files as a single output file. Collecting all of this...

I suspect that generating type definitions for *query results* would be more useful than table schemas, which become useless as soon as you select a subset of columns or follow...

Some breadcrumbs: From the `gmp-mpfr-sys` crate [README.md#Building on Windows](https://gitlab.com/tspiteri/gmp-mpfr-sys/-/blob/master/README.md#building-on-windows): > You can build on Windows with the Rust GNU toolchain and an up-to-date MSYS2 installation Maybe that would work for...