Feature: Add live flag to documents
See original GitHub issueSometimes a document needs to exist in the repository but not be rendered during build. i.e. the document should just be totally ignored by Grow.
This has arisen from some work that had been merged into our master branch which, at the last minute, we were asked to postpone the launch. The only way I know to do this currently, is to delete the yaml file, however this means that when we need to actually launch in a few days/weeks we’ll have to go hunting for the commit which deleted the yaml and revert it.
Perhaps having a $live
property on documents that defaults to true
, but can be set to false
if required would be a good idea?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Feature Flags—What Are Those? Uses, Benefits & Best ...
Feature flags are a software development concept that allow you to enable or disable a feature without modifying the source code or requiring...
Read more >Feature Flags: The Hidden Switch Behind Continuous ...
Feature flags allows you to ship code more frequently, test on production, and wow your users by revealing the feature at the right...
Read more >Essential Guide to Feature Flags - Split Software
A feature flag is a mechanism that allows you to choose between different code paths in your system at runtime. In this guide,...
Read more >Where to Store Feature Flags - Configuration Files vs ...
A look at the different ways feature flags can be stored based on their attributes: environment variables, configuration files, database, ...
Read more >Feature Toggles (aka Feature Flags) - Martin Fowler
Feature Toggles (often also refered to as Feature Flags) are a powerful technique, allowing teams to modify system behavior without changing code.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You should be able to now get this effect using the new syntax to disable it based on the environment:
Would cause it to be rendered everywhere but the
prod
env.@WillsB3 That error seems to be because it cannot find the default homepage. What do you have for the
home
value in your podspec? It needs to be something that has a serving path if you are using it as the home document.