chore(codegen): daily schema refresh (2026-05-18)#9
Open
timgl wants to merge 1 commit into
Open
Conversation
Adds docstrings to TrendsFilter (aggregationAxisFormat, aggregationAxisPrefix/Postfix, decimalPlaces). No structural changes; openapi-filter.yaml unchanged. Generated-By: PostHog Code Task-Id: dc9b071d-e37e-442f-aec0-cc3315a3c350
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Daily OpenAPI schema refresh against
https://us.posthog.com/api/schema/?format=json.Spec diff size: 15 lines added, 1 removed in
src/generated/api.d.ts. Purely docstring additions onTrendsFilter:aggregationAxisFormat— full description of the supported formats (numeric,duration,duration_ms,percentage,percentage_scaled,currency,short).aggregationAxisPostfix/aggregationAxisPrefix— guidance on when to use literal suffixes/prefixes vs picking the matching format.decimalPlaces— note on typical values for percentages and currency.No structural schema changes.
openapi-filter.yamlunchanged.Filter changes
None. No new operationIds added.
Resources touched
None. No client/pipeline edits required.
New operationIds in live spec (not added to filter)
The live spec exposes a very large set of operationIds outside the managed resource families (
action,cohort,dashboard,endpoint,event-definition,experiment,experiment-holdout,experiment-saved-metric,feature-flag,insight,project-settings,property-group). None of them are missing core CRUD ops for a managed family, so nothing was added.Notable categories that remain intentionally out of scope:
persons_*,groups_*,cohorts_persons_*,external_data_*,warehouse_*,llm_analytics_*,hog_flows_*,hog_functions_*,session_recordings_*,notebooks_*,surveys_*,error_tracking_*,logs_*,subscriptions_*,roles_*,members_*,organizations_*,tasks_*,tracing_spans_*,visual_review_*,signals_*, etc.environments_*mirrors of project-scoped routes (e.g.environments_insights_*,environments_dashboards_*) — duplicates of the routes we already use underprojects/*.actions_bulk_update_tags_create,actions_references_listcohorts_activity_retrieve,cohorts_all_activity_retrieve,cohorts_calculation_history_retrieve,cohorts_persons_retrieve,cohorts_add_persons_to_static_cohort_partial_update,cohorts_remove_person_from_static_cohort_partial_update,cohorts_update(PUT — we use PATCH)dashboards_*activity/collaborator/sharing/snapshot/copy/move/reorder helpers,dashboards_bulk_update_tags_createendpoints_*materialization/run/versions/last_execution_times helpersevent_definitions_bulk_update_tags_create,event_definitions_by_name_retrieve,event_definitions_metrics_retrieve,event_definitions_primary_properties_retrieve,event_definitions_{golang,python,typescript}_retrieve,event_definitions_update(PUT)event_schemas_partial_update,event_schemas_update(we only need list/create/destroy server-side)experiment_holdouts_update(PUT)experiment_saved_metrics_update(PUT)experiments_copy_to_project_create,experiments_create_exposure_cohort_for_experiment_create,experiments_duplicate_create,experiments_eligible_feature_flags_retrieve,experiments_recalculate_timeseries_create,experiments_requires_flag_implementation_retrieve,experiments_reset_create,experiments_ship_variant_create,experiments_stats_retrieve,experiments_timeseries_results_retrieve,experiments_update(PUT)feature_flags_*activity/dashboard/blast-radius/local-evaluation/remote-config/status/versions helpers,feature_flags_bulk_*insights_*activity/sharing/suggestions/thresholds/trending/viewed helpers,insights_bulk_update_tags_create,insights_analyze_retrieve,insights_my_last_viewed_retrieve,insights_cancel_create,insights_generate_metadata_createschema_property_groups_update(PUT)Convention: managed families intentionally use
PATCH(*_partial_update) and skipPUT(*_update) where both exist, except where the existing filter already includes_update(actions, insights, dashboards, feature_flags, endpoints) — left as-is in this PR.Unresolved drift
src/pull/run.test.ts > runPull orchestrator > writes files and calls tagOnServer on a non-dry runtimes out at 500ms under full-suite load (~318ms in isolation). Not caused by this refresh — schema change is doc-only. Suggest bumping the per-test timeout or relaxing this case.Test plan
pnpm install --frozen-lockfilepnpm codegenpnpm typecheckpnpm test(1 flaky timeout unrelated to schema; passes in isolation)TaskRun
Task-Id:
dc9b071d-e37e-442f-aec0-cc3315a3c350