-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: remove queryBuilderGrouping flag #16711
Conversation
fbd09e4
to
b60417a
Compare
return query | ||
} | ||
|
||
function buildQueryHelperButWithGrouping( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this diff is wonky. i renamed buildQueryHelperButWithGrouping
-> buildQueryFromConfig
and removed buildQueryHelper
which I thought could have been named a little clearly (hence buildQueryFromConfig
)
b60417a
to
ede22db
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks great.
whole thing makes me wonder if there should be a two stage approach (remove the flag, then revert the code at a later time) to allow for quicker rollbacks, but this might just be an artifact of not having a feature flagging service, so i'm not gonna think about it any more.
e4b38cf
to
eb643fe
Compare
eb643fe
to
af0d2bc
Compare
@drdelambre I think you're right, the point of a flagging system is to set it to So I started a new branch that just flips the flag the flag to |
Removes the
queryBuilderGrouping
flag, effectively turning the feature on.