Karl-Aksel Puulmann 8fa3a83129 APIv2: and/or/not support (#4480) ... * First approximation of AND/OR/NOT support Broken by this: - Goal filtering - Table deciding - Imports * TableDecider handle nesting * Query.remove_top_level_filters * Plausible.Stats.Imported.SQL.Expression * Handle AND/OR/NOT with imported data, create Plausible.Stats.Imported.SQL.WhereBuilder * Add parser validations for event:goal, event:hostname and event:props:x filters top level constraints * Move module around * Query.get_filter -> Filters.filtering_on_dimension? in some callsites * Filters.get_toplevel_filter * TableDecider.sessions_join_events?, remove old method * Transforming filters in query_optimizer * Query API tests for and/or/not * Reorder parser steps * Post-merge test fixups * Solve merge issue * Simplify filtering_on_dimension? * Update transformer code * dimensions_used_in_filters min_depth option, simplify parser validations * rename_dimensions_used_in_filter * fix rename_dimensions_used_in_filter * Rename a test		2024-09-04 15:44:03 +03:00
..
plausible	APIv2: and/or/not support (#4480)	2024-09-04 15:44:03 +03:00
plausible_web	Refactor and consolidate user session logic (#4452)	2024-08-23 10:53:33 +02:00
license.ex	Update license hash	2024-02-23 14:11:35 +02:00