Replies: 4 comments
-
Hi @benlesh! If this is still a thing I would create a list of all the operators that have enough arguments to get refactored to a config object. I would collect:
I would provide it as markdown like this:
Let me know if the suggested approach would be helpful or if I can adapt anything. |
Beta Was this translation helpful? Give feedback.
-
Thanks @BioPhoton.... we probably don't even need that level of detail. Just a list of the operators that have 3 or more arguments would be a great start. |
Beta Was this translation helpful? Give feedback.
-
Could you suggest a naming pattern? |
Beta Was this translation helpful? Give feedback.
-
Hi @benlesh! Here the list of operators/functions that have 3 or more arguments (n means infinite) Subjects
Creation Methode
Operators
|
Beta Was this translation helpful? Give feedback.
-
There are a few operators that have a lot of arguments, one example would be
groupBy
. This hurts readability a bit and also bites us later if we want to change or deprecate arguments.So the idea is simple, introduce non-breaking changes to operators like
groupBy
to allow the passing of a config object to essentially provide "named arguments":(The names can be bikeshedded later, ideally to make it more terse but still readable)
Beta Was this translation helpful? Give feedback.
All reactions