Deleted Post Deleted Post Deleted Post
2 Likes
There is also such a configuration flag for git integration.
Is anyone aware of a list of all these flags?
Preferably, the nightly would have an “advanced configuration” file, with all flags listed but disabled by default. and possibly some status information, such as “experimental”, “needs some more testing”, (and a date of when that comment was last updated.)
We deliberately don’t do this, because we want to be free to add/rename/delete these flags without people feeling like they are owed an update to some documentation. If you want to see a list of all the flags, you can look through the source code where the flags are defined. I don’t think it’s likely we would ever keep some separate documentation for them.
These flags are for developers only and while that doesn’t mean that everyone else can’t use them, it should also be done with the sense of “I’m using a thing that wasn’t made for me, it is not reasonable for me to expect things about this thing right now”
When things are behind these flags it is because they are have not finished being developed, not because they need testing. When we feel like things are to the stage where the next thing is that they need testing, the flag gets removed.
I don’t mean to discourage anyone from trying things out if they feel adventurous: it’s open-source after all! I just want people to have the right understanding of why these flags exist and therefore have the right spirit of adventure 
if looking up the source code to see what flags exists sounds way too hard, I would recommend taking that as a sign to not enable flags.
2 Likes