Skip to content

πŸ™Œ OpenHands: AI-Driven Development

chore(frontend): Remove `user_activated` PostHog capture event (#11704)

sp.wack5ad3572810cd
diff --git a/frontend/src/hooks/query/use-settings.ts b/frontend/src/hooks/query/use-settings.ts
index 957f65aa6e..74a516f4a6 100644
--- a/frontend/src/hooks/query/use-settings.ts
+++ b/frontend/src/hooks/query/use-settings.ts
@@ -1,6 +1,4 @@
import { useQuery } from "@tanstack/react-query";
-import React from "react";
-import posthog from "posthog-js";
import SettingsService from "#/settings-service/settings-service.api";
import { DEFAULT_SETTINGS } from "#/services/settings";
import { useIsOnTosPage } from "#/hooks/use-is-on-tos-page";
@@ -61,12 +59,6 @@ export const useSettings = () => {
},
});
- React.useEffect(() => {
- if (query.isFetched && query.data?.LLM_API_KEY_SET) {
- posthog.capture("user_activated");
- }
- }, [query.data?.LLM_API_KEY_SET, query.isFetched]);
-
// We want to return the defaults if the settings aren't found so the user can still see the
// options to make their initial save. We don't set the defaults in `initialData` above because
// that would prepopulate the data to the cache and mess with expectations. Read more: