[5.x] Ability to log fake queries by JohnathonKoster · Pull Request #9695 · statamic/cms

JohnathonKoster · 2024-03-10T19:54:38Z

Edit by Jason:

It's enabled by default if you have debug enabled. But you can override it and disable it if you want in config/statamic/system.php like this now:

-'fake_sql_queries' => config('app.debug'),+'fake_sql_queries' => false,

Queries will show up in Ray or Debugbar just like a regular database query. There's no need to opt into dumping values.

SQLite is now required (only for this fake query feature).

This PR adds the ability to log Stache "queries" like regular database queries. This is disabled by default. It can be configured by setting new configuration values within config/statamic/stache.php configuration file:

return [
// ..../* |-------------------------------------------------------------------------- | Query Logging |-------------------------------------------------------------------------- | | When enabled, the Stache query builders will log queries | like normal SQL Queries. To log actual query values, | set the dump_values configuration option to true. | */'query_logging' => [
'enabled' => false,
'dump_values' => false,
],
];

query_logging.enabled: Determines whether the query logger is enabled
query_logging.dump_values: Determines whether the query logger will dump "real" values or placeholders

When enabled, the query logger will emit Laravel's Illuminate\Database\Events\QueryExecuted event. This event will receive a database connection whose closure resolves to null, and no bindings.

By emitting this event existing tools, like Ray, DebugBar or Telescope will be able to pick up on the executed flat-file queries.

Example with dump_values set to false:

Example with dump_values set to true:

Important Note: The goal of this feature was not to output perfectly valid SQL statements, but rather to be able to observe what the Stache builders are doing in a familiar way with existing tools.

duncanmcclean · 2024-03-11T09:50:09Z

It might be nice if calling ->dd() on a query gave you the same thing?

Uses a real real in-memory sqlite connection. Small price to pay to make it simpler. Remove config option as we'll now always put values into bindings. Now that the QueryExecuted event is populated with more realistic data, bindings are automatically populated within the SQL when using Ray.

- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

- pass the query into the dumper class instead of a bunch of arguments - use a method on the trait to get all the appropriate wheres etc for the dumper - using that new method, provide the additional where clauses for the entries query that way instead of a "extra from statement" - remove dump trait method in favor of creating a new dumper

…will format to multiline automatically.

… filtering pages etc. move it to just the search query.

…e builders. removed the condition entirely. not sure when there would be no builder.

this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

jasonvarga · 2024-04-01T19:53:04Z

This was really cool. I couldn't help but make a bunch of tweaks. Now it looks more consistent with what happens with regular Laravel DB/Eloquent queries.

The event contains actual bindings so now we just always track them and they'll get replaced in the output where appropriate. There's no need for a separate opt-in setting for seeing values.
Moved things around quite a bit. Made it more generic. We have non-Stache query builders (like search).
I was able to clean things up significantly by using a real DB connection to an in-memory SQL database. The small downside it SQLite is required for this. Only for this feature though, not the whole CMS. Worth the trade off IMO.

JohnathonKoster · 2024-03-10T19:54:38Z

Edit by Jason:

It's enabled by default if you have debug enabled. But you can override it and disable it if you want in config/statamic/system.php like this now:

-'fake_sql_queries' => config('app.debug'),+'fake_sql_queries' => false,

Queries will show up in Ray or Debugbar just like a regular database query. There's no need to opt into dumping values.

SQLite is now required (only for this fake query feature).

This PR adds the ability to log Stache "queries" like regular database queries. This is disabled by default. It can be configured by setting new configuration values within config/statamic/stache.php configuration file:

return [
// ..../* |-------------------------------------------------------------------------- | Query Logging |-------------------------------------------------------------------------- | | When enabled, the Stache query builders will log queries | like normal SQL Queries. To log actual query values, | set the dump_values configuration option to true. | */'query_logging' => [
'enabled' => false,
'dump_values' => false,
],
];

query_logging.enabled: Determines whether the query logger is enabled
query_logging.dump_values: Determines whether the query logger will dump "real" values or placeholders

When enabled, the query logger will emit Laravel's Illuminate\Database\Events\QueryExecuted event. This event will receive a database connection whose closure resolves to null, and no bindings.

By emitting this event existing tools, like Ray, DebugBar or Telescope will be able to pick up on the executed flat-file queries.

Example with dump_values set to false:

Example with dump_values set to true:

Important Note: The goal of this feature was not to output perfectly valid SQL statements, but rather to be able to observe what the Stache builders are doing in a familiar way with existing tools.

duncanmcclean · 2024-03-11T09:50:09Z

It might be nice if calling ->dd() on a query gave you the same thing?

Uses a real real in-memory sqlite connection. Small price to pay to make it simpler. Remove config option as we'll now always put values into bindings. Now that the QueryExecuted event is populated with more realistic data, bindings are automatically populated within the SQL when using Ray.

- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

- pass the query into the dumper class instead of a bunch of arguments - use a method on the trait to get all the appropriate wheres etc for the dumper - using that new method, provide the additional where clauses for the entries query that way instead of a "extra from statement" - remove dump trait method in favor of creating a new dumper

…will format to multiline automatically.

… filtering pages etc. move it to just the search query.

…e builders. removed the condition entirely. not sure when there would be no builder.

this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

jasonvarga · 2024-04-01T19:53:04Z

This was really cool. I couldn't help but make a bunch of tweaks. Now it looks more consistent with what happens with regular Laravel DB/Eloquent queries.

The event contains actual bindings so now we just always track them and they'll get replaced in the output where appropriate. There's no need for a separate opt-in setting for seeing values.
Moved things around quite a bit. Made it more generic. We have non-Stache query builders (like search).
I was able to clean things up significantly by using a real DB connection to an in-memory SQL database. The small downside it SQLite is required for this. Only for this feature though, not the whole CMS. Worth the trade off IMO.

JohnathonKoster · 2024-03-10T19:54:38Z

Edit by Jason:

It's enabled by default if you have debug enabled. But you can override it and disable it if you want in config/statamic/system.php like this now:

-'fake_sql_queries' => config('app.debug'),+'fake_sql_queries' => false,

Queries will show up in Ray or Debugbar just like a regular database query. There's no need to opt into dumping values.

SQLite is now required (only for this fake query feature).

This PR adds the ability to log Stache "queries" like regular database queries. This is disabled by default. It can be configured by setting new configuration values within config/statamic/stache.php configuration file:

return [
// ..../* |-------------------------------------------------------------------------- | Query Logging |-------------------------------------------------------------------------- | | When enabled, the Stache query builders will log queries | like normal SQL Queries. To log actual query values, | set the dump_values configuration option to true. | */'query_logging' => [
'enabled' => false,
'dump_values' => false,
],
];

query_logging.enabled: Determines whether the query logger is enabled
query_logging.dump_values: Determines whether the query logger will dump "real" values or placeholders

When enabled, the query logger will emit Laravel's Illuminate\Database\Events\QueryExecuted event. This event will receive a database connection whose closure resolves to null, and no bindings.

By emitting this event existing tools, like Ray, DebugBar or Telescope will be able to pick up on the executed flat-file queries.

Example with dump_values set to false:

Example with dump_values set to true:

Important Note: The goal of this feature was not to output perfectly valid SQL statements, but rather to be able to observe what the Stache builders are doing in a familiar way with existing tools.

duncanmcclean · 2024-03-11T09:50:09Z

It might be nice if calling ->dd() on a query gave you the same thing?

Uses a real real in-memory sqlite connection. Small price to pay to make it simpler. Remove config option as we'll now always put values into bindings. Now that the QueryExecuted event is populated with more realistic data, bindings are automatically populated within the SQL when using Ray.

- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

- pass the query into the dumper class instead of a bunch of arguments - use a method on the trait to get all the appropriate wheres etc for the dumper - using that new method, provide the additional where clauses for the entries query that way instead of a "extra from statement" - remove dump trait method in favor of creating a new dumper

…will format to multiline automatically.

… filtering pages etc. move it to just the search query.

…e builders. removed the condition entirely. not sure when there would be no builder.

this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

jasonvarga · 2024-04-01T19:53:04Z

This was really cool. I couldn't help but make a bunch of tweaks. Now it looks more consistent with what happens with regular Laravel DB/Eloquent queries.

The event contains actual bindings so now we just always track them and they'll get replaced in the output where appropriate. There's no need for a separate opt-in setting for seeing values.
Moved things around quite a bit. Made it more generic. We have non-Stache query builders (like search).
I was able to clean things up significantly by using a real DB connection to an in-memory SQL database. The small downside it SQLite is required for this. Only for this feature though, not the whole CMS. Worth the trade off IMO.

JohnathonKoster · 2024-03-10T19:54:38Z

Edit by Jason:

It's enabled by default if you have debug enabled. But you can override it and disable it if you want in config/statamic/system.php like this now:

-'fake_sql_queries' => config('app.debug'),+'fake_sql_queries' => false,

Queries will show up in Ray or Debugbar just like a regular database query. There's no need to opt into dumping values.

SQLite is now required (only for this fake query feature).

This PR adds the ability to log Stache "queries" like regular database queries. This is disabled by default. It can be configured by setting new configuration values within config/statamic/stache.php configuration file:

return [
// ..../* |-------------------------------------------------------------------------- | Query Logging |-------------------------------------------------------------------------- | | When enabled, the Stache query builders will log queries | like normal SQL Queries. To log actual query values, | set the dump_values configuration option to true. | */'query_logging' => [
'enabled' => false,
'dump_values' => false,
],
];

query_logging.enabled: Determines whether the query logger is enabled
query_logging.dump_values: Determines whether the query logger will dump "real" values or placeholders

When enabled, the query logger will emit Laravel's Illuminate\Database\Events\QueryExecuted event. This event will receive a database connection whose closure resolves to null, and no bindings.

By emitting this event existing tools, like Ray, DebugBar or Telescope will be able to pick up on the executed flat-file queries.

Example with dump_values set to false:

Example with dump_values set to true:

Important Note: The goal of this feature was not to output perfectly valid SQL statements, but rather to be able to observe what the Stache builders are doing in a familiar way with existing tools.

duncanmcclean · 2024-03-11T09:50:09Z

It might be nice if calling ->dd() on a query gave you the same thing?

Uses a real real in-memory sqlite connection. Small price to pay to make it simpler. Remove config option as we'll now always put values into bindings. Now that the QueryExecuted event is populated with more realistic data, bindings are automatically populated within the SQL when using Ray.

- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

- pass the query into the dumper class instead of a bunch of arguments - use a method on the trait to get all the appropriate wheres etc for the dumper - using that new method, provide the additional where clauses for the entries query that way instead of a "extra from statement" - remove dump trait method in favor of creating a new dumper

…will format to multiline automatically.

… filtering pages etc. move it to just the search query.

…e builders. removed the condition entirely. not sure when there would be no builder.

this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

jasonvarga · 2024-04-01T19:53:04Z

This was really cool. I couldn't help but make a bunch of tweaks. Now it looks more consistent with what happens with regular Laravel DB/Eloquent queries.

The event contains actual bindings so now we just always track them and they'll get replaced in the output where appropriate. There's no need for a separate opt-in setting for seeing values.
Moved things around quite a bit. Made it more generic. We have non-Stache query builders (like search).
I was able to clean things up significantly by using a real DB connection to an in-memory SQL database. The small downside it SQLite is required for this. Only for this feature though, not the whole CMS. Worth the trade off IMO.

JohnathonKoster · 2024-03-10T19:54:38Z

Edit by Jason:

It's enabled by default if you have debug enabled. But you can override it and disable it if you want in config/statamic/system.php like this now:

-'fake_sql_queries' => config('app.debug'),+'fake_sql_queries' => false,

Queries will show up in Ray or Debugbar just like a regular database query. There's no need to opt into dumping values.

SQLite is now required (only for this fake query feature).

This PR adds the ability to log Stache "queries" like regular database queries. This is disabled by default. It can be configured by setting new configuration values within config/statamic/stache.php configuration file:

return [
// ..../* |-------------------------------------------------------------------------- | Query Logging |-------------------------------------------------------------------------- | | When enabled, the Stache query builders will log queries | like normal SQL Queries. To log actual query values, | set the dump_values configuration option to true. | */'query_logging' => [
'enabled' => false,
'dump_values' => false,
],
];

query_logging.enabled: Determines whether the query logger is enabled
query_logging.dump_values: Determines whether the query logger will dump "real" values or placeholders

When enabled, the query logger will emit Laravel's Illuminate\Database\Events\QueryExecuted event. This event will receive a database connection whose closure resolves to null, and no bindings.

By emitting this event existing tools, like Ray, DebugBar or Telescope will be able to pick up on the executed flat-file queries.

Example with dump_values set to false:

Example with dump_values set to true:

Important Note: The goal of this feature was not to output perfectly valid SQL statements, but rather to be able to observe what the Stache builders are doing in a familiar way with existing tools.

duncanmcclean · 2024-03-11T09:50:09Z

It might be nice if calling ->dd() on a query gave you the same thing?

Uses a real real in-memory sqlite connection. Small price to pay to make it simpler. Remove config option as we'll now always put values into bindings. Now that the QueryExecuted event is populated with more realistic data, bindings are automatically populated within the SQL when using Ray.

- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

- pass the query into the dumper class instead of a bunch of arguments - use a method on the trait to get all the appropriate wheres etc for the dumper - using that new method, provide the additional where clauses for the entries query that way instead of a "extra from statement" - remove dump trait method in favor of creating a new dumper

…will format to multiline automatically.

… filtering pages etc. move it to just the search query.

…e builders. removed the condition entirely. not sure when there would be no builder.

this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

jasonvarga · 2024-04-01T19:53:04Z

This was really cool. I couldn't help but make a bunch of tweaks. Now it looks more consistent with what happens with regular Laravel DB/Eloquent queries.

The event contains actual bindings so now we just always track them and they'll get replaced in the output where appropriate. There's no need for a separate opt-in setting for seeing values.
Moved things around quite a bit. Made it more generic. We have non-Stache query builders (like search).
I was able to clean things up significantly by using a real DB connection to an in-memory SQL database. The small downside it SQLite is required for this. Only for this feature though, not the whole CMS. Worth the trade off IMO.

JohnathonKoster · 2024-03-10T19:54:38Z

Edit by Jason:

It's enabled by default if you have debug enabled. But you can override it and disable it if you want in config/statamic/system.php like this now:

-'fake_sql_queries' => config('app.debug'),+'fake_sql_queries' => false,

Queries will show up in Ray or Debugbar just like a regular database query. There's no need to opt into dumping values.

SQLite is now required (only for this fake query feature).

This PR adds the ability to log Stache "queries" like regular database queries. This is disabled by default. It can be configured by setting new configuration values within config/statamic/stache.php configuration file:

return [
// ..../* |-------------------------------------------------------------------------- | Query Logging |-------------------------------------------------------------------------- | | When enabled, the Stache query builders will log queries | like normal SQL Queries. To log actual query values, | set the dump_values configuration option to true. | */'query_logging' => [
'enabled' => false,
'dump_values' => false,
],
];

query_logging.enabled: Determines whether the query logger is enabled
query_logging.dump_values: Determines whether the query logger will dump "real" values or placeholders

When enabled, the query logger will emit Laravel's Illuminate\Database\Events\QueryExecuted event. This event will receive a database connection whose closure resolves to null, and no bindings.

By emitting this event existing tools, like Ray, DebugBar or Telescope will be able to pick up on the executed flat-file queries.

Example with dump_values set to false:

Example with dump_values set to true:

Important Note: The goal of this feature was not to output perfectly valid SQL statements, but rather to be able to observe what the Stache builders are doing in a familiar way with existing tools.

duncanmcclean · 2024-03-11T09:50:09Z

It might be nice if calling ->dd() on a query gave you the same thing?

Uses a real real in-memory sqlite connection. Small price to pay to make it simpler. Remove config option as we'll now always put values into bindings. Now that the QueryExecuted event is populated with more realistic data, bindings are automatically populated within the SQL when using Ray.

- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

- pass the query into the dumper class instead of a bunch of arguments - use a method on the trait to get all the appropriate wheres etc for the dumper - using that new method, provide the additional where clauses for the entries query that way instead of a "extra from statement" - remove dump trait method in favor of creating a new dumper

…will format to multiline automatically.

… filtering pages etc. move it to just the search query.

…e builders. removed the condition entirely. not sure when there would be no builder.

this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

jasonvarga · 2024-04-01T19:53:04Z

This was really cool. I couldn't help but make a bunch of tweaks. Now it looks more consistent with what happens with regular Laravel DB/Eloquent queries.

The event contains actual bindings so now we just always track them and they'll get replaced in the output where appropriate. There's no need for a separate opt-in setting for seeing values.
Moved things around quite a bit. Made it more generic. We have non-Stache query builders (like search).
I was able to clean things up significantly by using a real DB connection to an in-memory SQL database. The small downside it SQLite is required for this. Only for this feature though, not the whole CMS. Worth the trade off IMO.

JohnathonKoster · 2024-03-10T19:54:38Z

Edit by Jason:

It's enabled by default if you have debug enabled. But you can override it and disable it if you want in config/statamic/system.php like this now:

-'fake_sql_queries' => config('app.debug'),+'fake_sql_queries' => false,

Queries will show up in Ray or Debugbar just like a regular database query. There's no need to opt into dumping values.

SQLite is now required (only for this fake query feature).

This PR adds the ability to log Stache "queries" like regular database queries. This is disabled by default. It can be configured by setting new configuration values within config/statamic/stache.php configuration file:

return [
// ..../* |-------------------------------------------------------------------------- | Query Logging |-------------------------------------------------------------------------- | | When enabled, the Stache query builders will log queries | like normal SQL Queries. To log actual query values, | set the dump_values configuration option to true. | */'query_logging' => [
'enabled' => false,
'dump_values' => false,
],
];

query_logging.enabled: Determines whether the query logger is enabled
query_logging.dump_values: Determines whether the query logger will dump "real" values or placeholders

When enabled, the query logger will emit Laravel's Illuminate\Database\Events\QueryExecuted event. This event will receive a database connection whose closure resolves to null, and no bindings.

By emitting this event existing tools, like Ray, DebugBar or Telescope will be able to pick up on the executed flat-file queries.

Example with dump_values set to false:

Example with dump_values set to true:

Important Note: The goal of this feature was not to output perfectly valid SQL statements, but rather to be able to observe what the Stache builders are doing in a familiar way with existing tools.

duncanmcclean · 2024-03-11T09:50:09Z

It might be nice if calling ->dd() on a query gave you the same thing?

Uses a real real in-memory sqlite connection. Small price to pay to make it simpler. Remove config option as we'll now always put values into bindings. Now that the QueryExecuted event is populated with more realistic data, bindings are automatically populated within the SQL when using Ray.

- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

- pass the query into the dumper class instead of a bunch of arguments - use a method on the trait to get all the appropriate wheres etc for the dumper - using that new method, provide the additional where clauses for the entries query that way instead of a "extra from statement" - remove dump trait method in favor of creating a new dumper

…will format to multiline automatically.

… filtering pages etc. move it to just the search query.

…e builders. removed the condition entirely. not sure when there would be no builder.

this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

jasonvarga · 2024-04-01T19:53:04Z

This was really cool. I couldn't help but make a bunch of tweaks. Now it looks more consistent with what happens with regular Laravel DB/Eloquent queries.

The event contains actual bindings so now we just always track them and they'll get replaced in the output where appropriate. There's no need for a separate opt-in setting for seeing values.
Moved things around quite a bit. Made it more generic. We have non-Stache query builders (like search).
I was able to clean things up significantly by using a real DB connection to an in-memory SQL database. The small downside it SQLite is required for this. Only for this feature though, not the whole CMS. Worth the trade off IMO.

JohnathonKoster · 2024-03-10T19:54:38Z

Edit by Jason:

It's enabled by default if you have debug enabled. But you can override it and disable it if you want in config/statamic/system.php like this now:

-'fake_sql_queries' => config('app.debug'),+'fake_sql_queries' => false,

Queries will show up in Ray or Debugbar just like a regular database query. There's no need to opt into dumping values.

SQLite is now required (only for this fake query feature).

This PR adds the ability to log Stache "queries" like regular database queries. This is disabled by default. It can be configured by setting new configuration values within config/statamic/stache.php configuration file:

return [
// ..../* |-------------------------------------------------------------------------- | Query Logging |-------------------------------------------------------------------------- | | When enabled, the Stache query builders will log queries | like normal SQL Queries. To log actual query values, | set the dump_values configuration option to true. | */'query_logging' => [
'enabled' => false,
'dump_values' => false,
],
];

query_logging.enabled: Determines whether the query logger is enabled
query_logging.dump_values: Determines whether the query logger will dump "real" values or placeholders

When enabled, the query logger will emit Laravel's Illuminate\Database\Events\QueryExecuted event. This event will receive a database connection whose closure resolves to null, and no bindings.

By emitting this event existing tools, like Ray, DebugBar or Telescope will be able to pick up on the executed flat-file queries.

Example with dump_values set to false:

Example with dump_values set to true:

Important Note: The goal of this feature was not to output perfectly valid SQL statements, but rather to be able to observe what the Stache builders are doing in a familiar way with existing tools.

duncanmcclean · 2024-03-11T09:50:09Z

It might be nice if calling ->dd() on a query gave you the same thing?

Uses a real real in-memory sqlite connection. Small price to pay to make it simpler. Remove config option as we'll now always put values into bindings. Now that the QueryExecuted event is populated with more realistic data, bindings are automatically populated within the SQL when using Ray.

- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

- pass the query into the dumper class instead of a bunch of arguments - use a method on the trait to get all the appropriate wheres etc for the dumper - using that new method, provide the additional where clauses for the entries query that way instead of a "extra from statement" - remove dump trait method in favor of creating a new dumper

…will format to multiline automatically.

… filtering pages etc. move it to just the search query.

…e builders. removed the condition entirely. not sure when there would be no builder.

this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

jasonvarga · 2024-04-01T19:53:04Z

This was really cool. I couldn't help but make a bunch of tweaks. Now it looks more consistent with what happens with regular Laravel DB/Eloquent queries.

The event contains actual bindings so now we just always track them and they'll get replaced in the output where appropriate. There's no need for a separate opt-in setting for seeing values.
Moved things around quite a bit. Made it more generic. We have non-Stache query builders (like search).
I was able to clean things up significantly by using a real DB connection to an in-memory SQL database. The small downside it SQLite is required for this. Only for this feature though, not the whole CMS. Worth the trade off IMO.

JohnathonKoster added 2 commits March 10, 2024 14:40

Adds support for logging Stache queries
c72935c

Update stache.php
1818006

This was referenced Mar 10, 2024
Document Stache query logging statamic/docs#1275
Closed
[5.x] Consolidated WIP Items #9588
Closed

JohnathonKoster added 2 commits March 10, 2024 15:20

Update LogsStacheQueries.php
4f3ea3a

Add extra FROM output from entry store
c524230

jasonvarga added 23 commits March 12, 2024 12:06

Merge branch 'master' into adds-stache-query-logging-support
8b71078

Merge branch 'master' into adds-stache-query-logging-support
dd3561a

fix merge
3dae5ee

stache is implied by namespace
dee1b0a

move into its own namespace
b0dd160

avoid property for enabling it
5e4f4e7

reuse it
131e08b

move to generic spot so it can be used in non-stache query builders
869aae4

move setting
929b7ff

tweaks ...
5e254ec
- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

use lowercase, it looks more like what laravel normally outputs
5a4236c

only dump the wheres in a nested where clause
dcc2825

avoid outputting "where" when there arent any
87bdff3

one-line everything. debugbar is weird when we provide newlines. ray …
575954d
…will format to multiline automatically.

wip
1bf8fdb

implement for assets
609db02

and terms
17c343d

dont fake queries in iterator builder, it's too much. we use that for…
ce548f9
… filtering pages etc. move it to just the search query.

move table name up a level
4adb4da

fix nested where not showing in search queries since they arent stach…
d85ab55
…e builders. removed the condition entirely. not sure when there would be no builder.

match was wrong. we wish it was that fast.
5d5817c

jasonvarga added 6 commits April 1, 2024 15:17

add onceWithColumns ported from laravel ...
fe32412
this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

apply fake queries to pluck
d489e6d

nitpick
b9a5579

nitpick
9bbb62c

nitpick
2975ace

nitpick
e191b87

just mirror the debug setting
2c1ef7d

jasonvarga changed the title ~~[5.x] Adds support for logging Stache queries~~[5.x] Adds support for logging fake queriesApr 1, 2024

jasonvarga changed the title ~~[5.x] Adds support for logging fake queries~~[5.x] Ability to log fake queriesApr 1, 2024

jasonvarga approved these changes Apr 1, 2024
View reviewed changes

jasonvarga merged commit 6b626b8 into statamic:masterApr 1, 2024

jasonvarga deleted the adds-stache-query-logging-support branch April 1, 2024 20:29

jasonvarga mentioned this pull request Apr 2, 2024
[5.x] Bump Laravel requirement to support DB::connectUsing()#9805
Merged

JohnathonKoster added 2 commits March 10, 2024 14:40

Adds support for logging Stache queries
c72935c

Update stache.php
1818006

This was referenced Mar 10, 2024
Document Stache query logging statamic/docs#1275
Closed
[5.x] Consolidated WIP Items #9588
Closed

JohnathonKoster added 2 commits March 10, 2024 15:20

Update LogsStacheQueries.php
4f3ea3a

Add extra FROM output from entry store
c524230

jasonvarga added 23 commits March 12, 2024 12:06

Merge branch 'master' into adds-stache-query-logging-support
8b71078

Merge branch 'master' into adds-stache-query-logging-support
dd3561a

fix merge
3dae5ee

stache is implied by namespace
dee1b0a

move into its own namespace
b0dd160

avoid property for enabling it
5e4f4e7

reuse it
131e08b

move to generic spot so it can be used in non-stache query builders
869aae4

move setting
929b7ff

tweaks ...
5e254ec
- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

use lowercase, it looks more like what laravel normally outputs
5a4236c

only dump the wheres in a nested where clause
dcc2825

avoid outputting "where" when there arent any
87bdff3

one-line everything. debugbar is weird when we provide newlines. ray …
575954d
…will format to multiline automatically.

wip
1bf8fdb

implement for assets
609db02

and terms
17c343d

dont fake queries in iterator builder, it's too much. we use that for…
ce548f9
… filtering pages etc. move it to just the search query.

move table name up a level
4adb4da

fix nested where not showing in search queries since they arent stach…
d85ab55
…e builders. removed the condition entirely. not sure when there would be no builder.

match was wrong. we wish it was that fast.
5d5817c

jasonvarga added 6 commits April 1, 2024 15:17

add onceWithColumns ported from laravel ...
fe32412
this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

apply fake queries to pluck
d489e6d

nitpick
b9a5579

nitpick
9bbb62c

nitpick
2975ace

nitpick
e191b87

just mirror the debug setting
2c1ef7d

jasonvarga changed the title ~~[5.x] Adds support for logging Stache queries~~[5.x] Adds support for logging fake queriesApr 1, 2024

jasonvarga changed the title ~~[5.x] Adds support for logging fake queries~~[5.x] Ability to log fake queriesApr 1, 2024

jasonvarga approved these changes Apr 1, 2024
View reviewed changes

jasonvarga merged commit 6b626b8 into statamic:masterApr 1, 2024

jasonvarga deleted the adds-stache-query-logging-support branch April 1, 2024 20:29

jasonvarga mentioned this pull request Apr 2, 2024
[5.x] Bump Laravel requirement to support DB::connectUsing()#9805
Merged

JohnathonKoster added 2 commits March 10, 2024 14:40

Adds support for logging Stache queries
c72935c

Update stache.php
1818006

This was referenced Mar 10, 2024
Document Stache query logging statamic/docs#1275
Closed
[5.x] Consolidated WIP Items #9588
Closed

JohnathonKoster added 2 commits March 10, 2024 15:20

Update LogsStacheQueries.php
4f3ea3a

Add extra FROM output from entry store
c524230

jasonvarga added 23 commits March 12, 2024 12:06

Merge branch 'master' into adds-stache-query-logging-support
8b71078

Merge branch 'master' into adds-stache-query-logging-support
dd3561a

fix merge
3dae5ee

stache is implied by namespace
dee1b0a

move into its own namespace
b0dd160

avoid property for enabling it
5e4f4e7

reuse it
131e08b

move to generic spot so it can be used in non-stache query builders
869aae4

move setting
929b7ff

tweaks ...
5e254ec
- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

use lowercase, it looks more like what laravel normally outputs
5a4236c

only dump the wheres in a nested where clause
dcc2825

avoid outputting "where" when there arent any
87bdff3

one-line everything. debugbar is weird when we provide newlines. ray …
575954d
…will format to multiline automatically.

wip
1bf8fdb

implement for assets
609db02

and terms
17c343d

dont fake queries in iterator builder, it's too much. we use that for…
ce548f9
… filtering pages etc. move it to just the search query.

move table name up a level
4adb4da

fix nested where not showing in search queries since they arent stach…
d85ab55
…e builders. removed the condition entirely. not sure when there would be no builder.

match was wrong. we wish it was that fast.
5d5817c

jasonvarga added 6 commits April 1, 2024 15:17

add onceWithColumns ported from laravel ...
fe32412
this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

apply fake queries to pluck
d489e6d

nitpick
b9a5579

nitpick
9bbb62c

nitpick
2975ace

nitpick
e191b87

just mirror the debug setting
2c1ef7d

jasonvarga changed the title ~~[5.x] Adds support for logging Stache queries~~[5.x] Adds support for logging fake queriesApr 1, 2024

jasonvarga changed the title ~~[5.x] Adds support for logging fake queries~~[5.x] Ability to log fake queriesApr 1, 2024

jasonvarga approved these changes Apr 1, 2024
View reviewed changes

jasonvarga merged commit 6b626b8 into statamic:masterApr 1, 2024

jasonvarga deleted the adds-stache-query-logging-support branch April 1, 2024 20:29

jasonvarga mentioned this pull request Apr 2, 2024
[5.x] Bump Laravel requirement to support DB::connectUsing()#9805
Merged

JohnathonKoster added 2 commits March 10, 2024 14:40

Adds support for logging Stache queries
c72935c

Update stache.php
1818006

This was referenced Mar 10, 2024
Document Stache query logging statamic/docs#1275
Closed
[5.x] Consolidated WIP Items #9588
Closed

JohnathonKoster added 2 commits March 10, 2024 15:20

Update LogsStacheQueries.php
4f3ea3a

Add extra FROM output from entry store
c524230

jasonvarga added 23 commits March 12, 2024 12:06

Merge branch 'master' into adds-stache-query-logging-support
8b71078

Merge branch 'master' into adds-stache-query-logging-support
dd3561a

fix merge
3dae5ee

stache is implied by namespace
dee1b0a

move into its own namespace
b0dd160

avoid property for enabling it
5e4f4e7

reuse it
131e08b

move to generic spot so it can be used in non-stache query builders
869aae4

move setting
929b7ff

tweaks ...
5e254ec
- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

use lowercase, it looks more like what laravel normally outputs
5a4236c

only dump the wheres in a nested where clause
dcc2825

avoid outputting "where" when there arent any
87bdff3

one-line everything. debugbar is weird when we provide newlines. ray …
575954d
…will format to multiline automatically.

wip
1bf8fdb

implement for assets
609db02

and terms
17c343d

dont fake queries in iterator builder, it's too much. we use that for…
ce548f9
… filtering pages etc. move it to just the search query.

move table name up a level
4adb4da

fix nested where not showing in search queries since they arent stach…
d85ab55
…e builders. removed the condition entirely. not sure when there would be no builder.

match was wrong. we wish it was that fast.
5d5817c

jasonvarga added 6 commits April 1, 2024 15:17

add onceWithColumns ported from laravel ...
fe32412
this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

apply fake queries to pluck
d489e6d

nitpick
b9a5579

nitpick
9bbb62c

nitpick
2975ace

nitpick
e191b87

just mirror the debug setting
2c1ef7d

jasonvarga changed the title ~~[5.x] Adds support for logging Stache queries~~[5.x] Adds support for logging fake queriesApr 1, 2024

jasonvarga changed the title ~~[5.x] Adds support for logging fake queries~~[5.x] Ability to log fake queriesApr 1, 2024

jasonvarga approved these changes Apr 1, 2024
View reviewed changes

jasonvarga merged commit 6b626b8 into statamic:masterApr 1, 2024

jasonvarga deleted the adds-stache-query-logging-support branch April 1, 2024 20:29

jasonvarga mentioned this pull request Apr 2, 2024
[5.x] Bump Laravel requirement to support DB::connectUsing()#9805
Merged

JohnathonKoster added 2 commits March 10, 2024 14:40

Adds support for logging Stache queries
c72935c

Update stache.php
1818006

This was referenced Mar 10, 2024
Document Stache query logging statamic/docs#1275
Closed
[5.x] Consolidated WIP Items #9588
Closed

JohnathonKoster added 2 commits March 10, 2024 15:20

Update LogsStacheQueries.php
4f3ea3a

Add extra FROM output from entry store
c524230

jasonvarga added 23 commits March 12, 2024 12:06

Merge branch 'master' into adds-stache-query-logging-support
8b71078

Merge branch 'master' into adds-stache-query-logging-support
dd3561a

fix merge
3dae5ee

stache is implied by namespace
dee1b0a

move into its own namespace
b0dd160

avoid property for enabling it
5e4f4e7

reuse it
131e08b

move to generic spot so it can be used in non-stache query builders
869aae4

move setting
929b7ff

tweaks ...
5e254ec
- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

use lowercase, it looks more like what laravel normally outputs
5a4236c

only dump the wheres in a nested where clause
dcc2825

avoid outputting "where" when there arent any
87bdff3

one-line everything. debugbar is weird when we provide newlines. ray …
575954d
…will format to multiline automatically.

wip
1bf8fdb

implement for assets
609db02

and terms
17c343d

dont fake queries in iterator builder, it's too much. we use that for…
ce548f9
… filtering pages etc. move it to just the search query.

move table name up a level
4adb4da

fix nested where not showing in search queries since they arent stach…
d85ab55
…e builders. removed the condition entirely. not sure when there would be no builder.

match was wrong. we wish it was that fast.
5d5817c

jasonvarga added 6 commits April 1, 2024 15:17

add onceWithColumns ported from laravel ...
fe32412
this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

apply fake queries to pluck
d489e6d

nitpick
b9a5579

nitpick
9bbb62c

nitpick
2975ace

nitpick
e191b87

just mirror the debug setting
2c1ef7d

jasonvarga changed the title ~~[5.x] Adds support for logging Stache queries~~[5.x] Adds support for logging fake queriesApr 1, 2024

jasonvarga changed the title ~~[5.x] Adds support for logging fake queries~~[5.x] Ability to log fake queriesApr 1, 2024

jasonvarga approved these changes Apr 1, 2024
View reviewed changes

jasonvarga merged commit 6b626b8 into statamic:masterApr 1, 2024

jasonvarga deleted the adds-stache-query-logging-support branch April 1, 2024 20:29

jasonvarga mentioned this pull request Apr 2, 2024
[5.x] Bump Laravel requirement to support DB::connectUsing()#9805
Merged

JohnathonKoster added 2 commits March 10, 2024 14:40

Adds support for logging Stache queries
c72935c

Update stache.php
1818006

This was referenced Mar 10, 2024
Document Stache query logging statamic/docs#1275
Closed
[5.x] Consolidated WIP Items #9588
Closed

JohnathonKoster added 2 commits March 10, 2024 15:20

Update LogsStacheQueries.php
4f3ea3a

Add extra FROM output from entry store
c524230

jasonvarga added 23 commits March 12, 2024 12:06

Merge branch 'master' into adds-stache-query-logging-support
8b71078

Merge branch 'master' into adds-stache-query-logging-support
dd3561a

fix merge
3dae5ee

stache is implied by namespace
dee1b0a

move into its own namespace
b0dd160

avoid property for enabling it
5e4f4e7

reuse it
131e08b

move to generic spot so it can be used in non-stache query builders
869aae4

move setting
929b7ff

tweaks ...
5e254ec
- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

use lowercase, it looks more like what laravel normally outputs
5a4236c

only dump the wheres in a nested where clause
dcc2825

avoid outputting "where" when there arent any
87bdff3

one-line everything. debugbar is weird when we provide newlines. ray …
575954d
…will format to multiline automatically.

wip
1bf8fdb

implement for assets
609db02

and terms
17c343d

dont fake queries in iterator builder, it's too much. we use that for…
ce548f9
… filtering pages etc. move it to just the search query.

move table name up a level
4adb4da

fix nested where not showing in search queries since they arent stach…
d85ab55
…e builders. removed the condition entirely. not sure when there would be no builder.

match was wrong. we wish it was that fast.
5d5817c

jasonvarga added 6 commits April 1, 2024 15:17

add onceWithColumns ported from laravel ...
fe32412
this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

apply fake queries to pluck
d489e6d

nitpick
b9a5579

nitpick
9bbb62c

nitpick
2975ace

nitpick
e191b87

just mirror the debug setting
2c1ef7d

jasonvarga changed the title ~~[5.x] Adds support for logging Stache queries~~[5.x] Adds support for logging fake queriesApr 1, 2024

jasonvarga changed the title ~~[5.x] Adds support for logging fake queries~~[5.x] Ability to log fake queriesApr 1, 2024

jasonvarga approved these changes Apr 1, 2024
View reviewed changes

jasonvarga merged commit 6b626b8 into statamic:masterApr 1, 2024

jasonvarga deleted the adds-stache-query-logging-support branch April 1, 2024 20:29

jasonvarga mentioned this pull request Apr 2, 2024
[5.x] Bump Laravel requirement to support DB::connectUsing()#9805
Merged

JohnathonKoster added 2 commits March 10, 2024 14:40

Adds support for logging Stache queries
c72935c

Update stache.php
1818006

This was referenced Mar 10, 2024
Document Stache query logging statamic/docs#1275
Closed
[5.x] Consolidated WIP Items #9588
Closed

JohnathonKoster added 2 commits March 10, 2024 15:20

Update LogsStacheQueries.php
4f3ea3a

Add extra FROM output from entry store
c524230

jasonvarga added 23 commits March 12, 2024 12:06

Merge branch 'master' into adds-stache-query-logging-support
8b71078

Merge branch 'master' into adds-stache-query-logging-support
dd3561a

fix merge
3dae5ee

stache is implied by namespace
dee1b0a

move into its own namespace
b0dd160

avoid property for enabling it
5e4f4e7

reuse it
131e08b

move to generic spot so it can be used in non-stache query builders
869aae4

move setting
929b7ff

tweaks ...
5e254ec
- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

use lowercase, it looks more like what laravel normally outputs
5a4236c

only dump the wheres in a nested where clause
dcc2825

avoid outputting "where" when there arent any
87bdff3

one-line everything. debugbar is weird when we provide newlines. ray …
575954d
…will format to multiline automatically.

wip
1bf8fdb

implement for assets
609db02

and terms
17c343d

dont fake queries in iterator builder, it's too much. we use that for…
ce548f9
… filtering pages etc. move it to just the search query.

move table name up a level
4adb4da

fix nested where not showing in search queries since they arent stach…
d85ab55
…e builders. removed the condition entirely. not sure when there would be no builder.

match was wrong. we wish it was that fast.
5d5817c

jasonvarga added 6 commits April 1, 2024 15:17

add onceWithColumns ported from laravel ...
fe32412
this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

apply fake queries to pluck
d489e6d

nitpick
b9a5579

nitpick
9bbb62c

nitpick
2975ace

nitpick
e191b87

just mirror the debug setting
2c1ef7d

jasonvarga changed the title ~~[5.x] Adds support for logging Stache queries~~[5.x] Adds support for logging fake queriesApr 1, 2024

jasonvarga changed the title ~~[5.x] Adds support for logging fake queries~~[5.x] Ability to log fake queriesApr 1, 2024

jasonvarga approved these changes Apr 1, 2024
View reviewed changes

jasonvarga merged commit 6b626b8 into statamic:masterApr 1, 2024

jasonvarga deleted the adds-stache-query-logging-support branch April 1, 2024 20:29

jasonvarga mentioned this pull request Apr 2, 2024
[5.x] Bump Laravel requirement to support DB::connectUsing()#9805
Merged

JohnathonKoster added 2 commits March 10, 2024 14:40

Adds support for logging Stache queries
c72935c

Update stache.php
1818006

This was referenced Mar 10, 2024
Document Stache query logging statamic/docs#1275
Closed
[5.x] Consolidated WIP Items #9588
Closed

JohnathonKoster added 2 commits March 10, 2024 15:20

Update LogsStacheQueries.php
4f3ea3a

Add extra FROM output from entry store
c524230

jasonvarga added 23 commits March 12, 2024 12:06

Merge branch 'master' into adds-stache-query-logging-support
8b71078

Merge branch 'master' into adds-stache-query-logging-support
dd3561a

fix merge
3dae5ee

stache is implied by namespace
dee1b0a

move into its own namespace
b0dd160

avoid property for enabling it
5e4f4e7

reuse it
131e08b

move to generic spot so it can be used in non-stache query builders
869aae4

move setting
929b7ff

tweaks ...
5e254ec
- rename trait to fakesqueries - rework to a closure based method that does the timing etc - add to iterator builder - pass table name rather than store, and add methods for figuring out the names - add to iterator builder (e.g. search)

use lowercase, it looks more like what laravel normally outputs
5a4236c

only dump the wheres in a nested where clause
dcc2825

avoid outputting "where" when there arent any
87bdff3

one-line everything. debugbar is weird when we provide newlines. ray …
575954d
…will format to multiline automatically.

wip
1bf8fdb

implement for assets
609db02

and terms
17c343d

dont fake queries in iterator builder, it's too much. we use that for…
ce548f9
… filtering pages etc. move it to just the search query.

move table name up a level
4adb4da

fix nested where not showing in search queries since they arent stach…
d85ab55
…e builders. removed the condition entirely. not sure when there would be no builder.

match was wrong. we wish it was that fast.
5d5817c

jasonvarga added 6 commits April 1, 2024 15:17

add onceWithColumns ported from laravel ...
fe32412
this allows to avoid the `$this->columns ?? $columns` situation. `$this->columns` will always be what you need. also fixes `$query->get(['col1', 'col2'])` not showing proper `select`ed columns within our fake queries

apply fake queries to pluck
d489e6d

nitpick
b9a5579

nitpick
9bbb62c

nitpick
2975ace

nitpick
e191b87

just mirror the debug setting
2c1ef7d

jasonvarga changed the title ~~[5.x] Adds support for logging Stache queries~~[5.x] Adds support for logging fake queriesApr 1, 2024

jasonvarga changed the title ~~[5.x] Adds support for logging fake queries~~[5.x] Ability to log fake queriesApr 1, 2024

jasonvarga approved these changes Apr 1, 2024
View reviewed changes

jasonvarga merged commit 6b626b8 into statamic:masterApr 1, 2024

jasonvarga deleted the adds-stache-query-logging-support branch April 1, 2024 20:29

jasonvarga mentioned this pull request Apr 2, 2024
[5.x] Bump Laravel requirement to support DB::connectUsing()#9805
Merged

Uh oh!

Uh oh!

Conversation

JohnathonKoster commented Mar 10, 2024• edited by jasonvarga Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duncanmcclean commented Mar 11, 2024

Uh oh!

jasonvarga commented Apr 1, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

JohnathonKoster commented Mar 10, 2024• edited by jasonvarga Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duncanmcclean commented Mar 11, 2024

Uh oh!

jasonvarga commented Apr 1, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

JohnathonKoster commented Mar 10, 2024• edited by jasonvarga Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duncanmcclean commented Mar 11, 2024

Uh oh!

jasonvarga commented Apr 1, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

JohnathonKoster commented Mar 10, 2024• edited by jasonvarga Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

duncanmcclean commented Mar 11, 2024

Uh oh!

jasonvarga commented Apr 1, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

JohnathonKoster commented Mar 10, 2024• edited by jasonvarga Loading Uh oh! There was an error while loading. Please reload this page.

JohnathonKoster commented Mar 10, 2024•
edited by jasonvarga
Loading

jasonvarga commented Apr 1, 2024•
edited
Loading

JohnathonKoster commented Mar 10, 2024•
edited by jasonvarga
Loading

jasonvarga commented Apr 1, 2024•
edited
Loading

JohnathonKoster commented Mar 10, 2024•
edited by jasonvarga
Loading

jasonvarga commented Apr 1, 2024•
edited
Loading

JohnathonKoster commented Mar 10, 2024•
edited by jasonvarga
Loading

jasonvarga commented Apr 1, 2024•
edited
Loading

JohnathonKoster commented Mar 10, 2024•
edited by jasonvarga
Loading

jasonvarga commented Apr 1, 2024•
edited
Loading

JohnathonKoster commented Mar 10, 2024•
edited by jasonvarga
Loading

jasonvarga commented Apr 1, 2024•
edited
Loading