feat(schema-migrations): upgrade hardcoded frontend queries in place

[thmsobrmlr]

Reverts the revert #34045

#33650

[github-actions]

Size Change: +3.1 kB (+0.12%)

Total Size: 2.58 MB

Filename	Size	Change
frontend/dist/toolbar.js	2.58 MB	+3.1 kB (+0.12%)

_{compressed-size-action}

[greptile-apps]

PR Summary

This PR reintroduces the schema migration system for frontend queries by implementing version control through the setLatestVersionsOnQuery utility, ensuring consistent schema versioning across the application.

• Added version control to Monaco editor components in frontend/src/lib/monaco/codeEditorLogic.tsx and hogQLAutocompleteProvider.ts to ensure proper schema versioning during query editing and autocompletion
• Refactored getFreshQuery to setLatestVersionsOnQuery in frontend/src/queries/utils.ts with new recursion control feature for fine-grained version management
• Applied versioning across critical query components (experiments, funnels, retention) with explicit recursion control to prevent deep recursion issues
• Enhanced HogQL query handling in frontend/src/lib/api.ts to ensure version consistency before backend transmission
• Added comprehensive test coverage in frontend/src/queries/utils.setLatestVersionsOnQuery.test.ts for both recursive and non-recursive version setting

_{23 files reviewed, 1 comment
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: Consider moving the common options object { recursion: false } to a constant since it's used twice

[andehen]

Tested the branch locally, and experiment queries are working fine ✅

Is wrapping the input to performQuery with setLatestVersionsOnQuery something temporary, or something we need to care about in the future?

[thmsobrmlr]

Tested the branch locally, and experiment queries are working fine ✅

Is wrapping the input to performQuery with setLatestVersionsOnQuery something temporary, or something we need to care about in the future?

This is part of a schema migrations system that will allow us to evolve the query schema e.g. changing a boolean property to an enum. The system makes the assumption that nodes without an explicit version are version 1. As such we need to set the latest version on each node that we know to be in the current schema i.e. for all hardcoded parts of queries.