Feature Flags and and other demo branches #877
Replies: 1 comment 1 reply
-
|
Everything is subject to change :) Feature flags currently depend on the TanStack DB & Electric SQL branch. I use it on my side project, but I don't know if it will ever be merged. The TanStack DB & Electric SQL combo is truly a game changer, but it requires an extra container per database in Azure. Feature flags are on my "Someday Maybe" roadmap: Roadmap The demos are just that. When I do talks, I "vibe" code new features and sometimes push them so people can see the code. They are not planned in any way. But the two you mentioned are so simple that you might just pull them in. But overall, remember that PlatformPlatform is boilerplate code. I make no promises that you'll easily get updates, and I often make breaking changes. I do have a pull-platformplatform-changes CLI command, but it's a best-effort approach, and will almost certainly give you merge conflicts. If you want to update, the best way is to ask an AI like Claude Code to pull in changes from a specific pull request. This is what I do on my side projects, and how other downstream projects get updates. I even pull updates the other way too. I might change pull-platformplatform-changes to be AI-driven and make a Skill for pulling changes. But not sure if/when that will be prioritized :) TL;DR: in the world of AI, things move too fast, and the old way of micromanaging updates and merge conflicts is too slow when you can just ask the AI to code the features you want. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Thomas,
I also wanted to ask about some of the other branches in the repo. I noticed a few of them are labeled as demos (like
demo/teamsanddemo/contact-information), while others likefeature-flagsexist without the demo tag.What are the plans for these branches? Will the demo features eventually make their way into
main, or are they mainly meant as reference implementations?The Teams and Contact Information features in particular are actually quite important for my upcoming SaaS, so I just want to understand whether I should plan around them being merged, or treat them more as examples to implement myself.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions