Using Ruby version: 3.1.2
- Run
bundle - Run
rails db:purge db:create db:migrate db:seed - Run
rails server
Hey! Wanted to share a Rails project I was hacking on over the Holiday!
My main goal here was just to get more experience building things with Rails by starting from scratch. I thought it’d be fun to attempt building our “Root experience dashboard” so that when it comes time for the team to build it for real, I’ll hopefully have more useful thoughts and questions. Comparing how I accomplished things in Rails vs how Shivang or Vishal will accomplish them will help me learn. The way I modeled this is pretty simple (maybe not realistic but good for my experience):
A Feature is basically just a container that can hold, Enabled, Condition, and/or Bucket models.
In the old root-server/.env file we would’ve used two different envvars for something like:
PAID_REFFERALS_ENABLED and PAID_REFFERAL_MARKETS. But a Feature lets you group those kinds of related things together.
The dashboard lets you search for what you’re looking for and if you click into a feature you can make certain changes.
- Allow the use of natural language for feature names.
- Included a description for how the feature works.
- Hide the further details until a user finds what they want. Then allow them to expand the panel and see more.
- It’s all read only on the main page so Designers and Product peeps don’t have to worry about accidentally disabling something. (The two clicks to get into edit is intentional friction)
- Only engineers can create new features. Product is only provided the ability to modify existing features.
- The search can be improved but it adds quality of life to a world where there are hundreds of features.
- I envision having something like tags that would let you filter by team. “I only want to see features that my team owns”.
Add tags to features allowing you to filter them by team or other criteria.