Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alltime compare sentry error #3203

Merged
merged 2 commits into from
Feb 4, 2021
Merged

Alltime compare sentry error #3203

merged 2 commits into from
Feb 4, 2021

Conversation

EDsCODE
Copy link
Member

@EDsCODE EDsCODE commented Feb 4, 2021

Changes

Please describe.

  • fixes this sentry error
  • trying to use compare on all time should be disabled. I moved this logic to the comparefilterlogic so that it's fully contained
  • also fixes enum issue that was breaking remove-shownas flag along with this sentry error

If this affects the frontend, include screenshots.

Checklist

  • All querysets/queries filter by Organization, by Team, and by User
  • Django backend tests
  • Jest frontend tests
  • Cypress end-to-end tests

@EDsCODE EDsCODE requested a review from macobo February 4, 2021 15:35
@timgl timgl temporarily deployed to posthog-alltime-compare-lnraml February 4, 2021 15:38 Inactive
actions.setCompare(compare)
}
if (shown_as === ShownAsValue.LIFECYCLE || date_from === 'all') {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this make more sense as a selector rather than a separate action?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm can you pull searchparams in selector arguments? I've never done it before but if possible yeah we could move it there.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah. Didn't realize it was search params - do we store them somewhere else (e.g. a related logic) - if so, connecting + selector might be cleaner.

This is nitpicking though, all else lgtm.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

connected to the router. I tried giving it a shot actually but it wasn't really making sense to me

Copy link
Contributor

@macobo macobo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gonna leave whether to implement selector up to you :)

@EDsCODE EDsCODE merged commit 2a28955 into master Feb 4, 2021
@EDsCODE EDsCODE deleted the alltime-compare-sentry-error branch February 4, 2021 21:28
@sentry-io
Copy link

sentry-io bot commented Feb 5, 2021

Sentry issue: POSTHOG-23D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants