-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Rename GridFilterModel['linkOperator']
to GridFilterModel['logicOperator']
and same for translations
#7270
Comments
Is there truly a need for a prefix like I say this because when you abstract away the client-side stuff, as an external dev using server-side everything, the prefix is irrelevant and honestly more confusing when explaining to the team than not. Explaining to people that it's just a generic operator name that is mapped to the actual operator, especially in other languages and when applied via ORM's The context read, from the discussion of operators and rules, like you may choose to separate those which I think would make the server-side pagination model more challenging to work with. EDIT: |
I would disagree. For me, it implies that it is composable. There can't be multiple operators between filters to do a |
The "logicOperator" seems to be more explicit than the generic "operator". I don't think we should aim to map everything to server-side naming or conventions. |
That's fair. I don't view it as catering only to server-side as you state, in client-only mode you aren't adding any unique functionality that differs from server-side to say that this is making it about the server-side only. If you'd like to follow Mongo though, have at it, nothing I will really be able to say to change your thoughts on an opinion-only topic, just weighing in that at least one customer disagrees with this change. 🤷♂️ |
Naming things is hard 🙂 |
Context: #3915 (comment)
The text was updated successfully, but these errors were encountered: