Closed mistercrunch closed 1 week ago
Maybe it would be interesting to have link to FEATURE_FLAGS.md at the top of FEATURE_FLAGS
section.
Agreed, though I hate having fragmented information about flags in config.py and in FEATURE_FLAGS.md, we should migrate/merge all intel in one place and reference it from others.
Maybe the larger task here is to merge what's in config.py onto FEATURE_FLAGS.md, clean it up and reference it from config.py?
@rusackas and @sadpandajoe had some ideas on how to improve this. I agree with the idea of keeping things in just one place.
Agree on having a single source of truth. I think the other problem right now is that the config file with comments is huge so i'd vote to moving it to the .md file. One thing I was thinking about is just sectioning things like we do in the feature flag file, might be a bit more work, but then we don't have to comment as much as which ones are stable, which ones are testing and so on.
Hey can we merge this as is, and defer to another task/issue of merging the content/comments in config.py into FEATURE_FLAGS.md?
Hey can we merge this as is, and defer to another task/issue of merging the content/comments in config.py into FEATURE_FLAGS.md?
@mistercrunch yeah, these would be follow-ups and not a blocker for this PR
Not sure if we're all aligned on this, but I've seen confusion around GLOBAL_ASYNC_QUERIES and the reality is we shouldn't recommend flipping this on until we iron out at least a few things. This comment I'm adding makes it a bit more clear you should steer away unless you know what you're doing