-
Notifications
You must be signed in to change notification settings - Fork 483
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
Array 1.43.0 #5025
Array 1.43.0 #5025
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
"highlight" PRs:
chore(flags): Remove flag for variant overrides highlight ⭐Release highlight |
Curated list of commits since the last version
|
across PostHog/posthog#12959, PostHog/posthog#13351, and PostHog/posthog#12544 I'd say something like: Searching by tags and descriptions is now 1,000,000%(approx) easier |
PostHog/posthog#13018 might be worth highlighting because periodically people ask to be able to show the legend on a pie chart on a dashboard... You already can, but before it was so ugly that I never wanted to 😓 |
Thanks Ben! This is kinda a long list, especially if there are more which @macobo wants to add on performance-wise. Are there any here which you think are less highlight-worthy? I'd like the highlights to be quite sizable and exciting, so an uneducated guess may be that we cut it down too... Highlights
Other fixes and improvements
Highlights would get a full description and commentary, other fixes get a single line and link to the PR. |
Co-authored-by: Neil Kakkar <neilkakkar@gmail.com>
…into array-1-43-0
Is it better to have performance as one highlight? Then we can say "here's how we approached it" -> let Karl loose And "look at how much we achieved" -> car-salesman-patting-roof-of-car.meme |
That'd be ideal from my perspective, but I'll defer by default to what the improvements are in Karl's mind first! |
This should now be ready for any final reviews. @macobo There was quite a lot of performance improvement copy, so I've edited it quite aggressively -- you may want to take a look just to Joe-proof it! 🙏 |
I also wanna add PostHog/posthog#12773 as a highlight. I checked it in the list above – I thought you Ben & Joe planned to use that list to include things in the changelog, but I can also write the note. 😅 |
My bad! I can add and write it up in a sec |
- [New: Feature flag variant overrides](#new-feature-flag-variant-overrides) | ||
- [New: Export recordings to file](#new-export-recordings-to-file) | ||
- [New: Better insight searching](#new-better-insight-searching) | ||
- [New: Show event/property counts in persons modal](#new-show-eventproperty-counts-in-persons-modal) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't point to a paragraph yet – just to be explicit, should I write one or would you prefer to take over this @joethreepwood?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, I've written one and got a gif. Something is up with this PR which is giving me grief though. Let me try to add it in again.
Right the final addition should be in. I've also added GIFs for all NEW items, and moved improvements to the end so that the focus is on new features |
(on mobile, haven't previewed)
@corywatilo Going to revert to the normal image on this btw, unless you can point me to a Figma? Artifacting is noticeable and there’s a black line on the right side |
This is covered by the pinned TOC
Changes
Draft of new array blog post, ft. @macobo and @benjackwhite
In order to meet deadlines for @corywatilo to shoot video, we must lock content down by Thursday 13th Jan, for publishing on Monday 16th Jan.
Checklist