Our primary goals for this release were to iron out bugs and improve the user experience of our Beta features.
As a result, we fixed a whole lot of stuff. We merged dozens of PRs with session recording fixes and improvements, and a dozen more with updates to our apps functionality. We also improved things like event ingestion, the UX for feature flags, and our settings for both organizations and projects. You can read through the entire list of fixes later in this post, but beware: it's quite long.
Finally, thank you to everyone who helped us out with feedback and contributions during this release cycle, you help us make PostHog better every day.
If you're self-hosting and want to upgrade for a better experience with nicer features, remember to update your PostHog instance.
We upgraded our event selection box to include actions and events in one, as well as provide smarter recommendations of events and actions you might want to use of based frequently used in queries by you or your team.
A new version of posthog-js is available and we recommend you to update if you've installed it via npm. Snippet users have access to the latest version by default.
The new version includes a lot of bugfixes that improve our session recording feature, as well as is significantly lighter, having had a lot of legacy code removed.
R.I.P. to the hundreds of lines of JavaScript that were removed - you will not be missed.
Following feedback from a user, we have now added support for PostHog Apps to our Helm chart.
If you're using the chart to deploy PostHog, upgrading to the latest version will give you access to the new app server (Beta).
Out of the many improvements to session recording, there are some worth mentioning specifically:
spacebar to pause/play, f to open player in full screen)Our codebase now disallows bracket-less control structures, enforcing curly brackets on if statements for unbeatable readability.
As described by Michael, one of our engineers:
"They don't do anything, yet we thank them for their existence."
We'd love to hear anything you have to say about PostHog, good or bad. As a thank you, we'll share some awesome PostHog merch.
Want to get involved? Email us to schedule a 30 minute call with one of our teams to help us make PostHog even better!
If you didn't already know, in the interest of transparency, we plan our next releases openly on GitHub, so you can always keep up with what we're up to during a release cycle.
Big thanks to the following members of our community who have contributed to PostHog over this release cycle:
Are you a Lead Designer or Fullstack Engineer?
Or perhaps you're not either but think you'd still be a good fit for PostHog?
In addition to the highlights listed above, we also merged a bunch of PRs improving PostHog's performance and fixing bugs:
posthog.json plugin support #2449 (mariusandra)Want to just try it already?
(Sorry for the shameless CTA.)
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。