Initialize Disabled Posthog Instance When API Key is Not Present #239
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.
This PR addresses the issue of initializing a disabled
posthog
instance when thePOSTHOG_API_KEY
is not present.Previously, the
posthog
instance was set toNone
when thePOSTHOG_API_KEY
was not present. This has been modified so that a disabledposthog
instance is initialized instead.Additionally, a log statement at the warning level has been added to indicate the initialization of the empty
posthog
instance. This will aid in debugging and understanding the state of the application.The changes are made in the
sweepai/utils/event_logger.py
file.Fixes #236.
To checkout this PR branch, run the following command in your terminal: