Provide possibility to use only specific operators
See original GitHub issueHello,
You are working on the awesome project 😃 And I’d like to use it inside my library. The only issue is bundle size.
So, I want to request possibility to use only specific query operators. For example, I want to use only query operators and simple operators. I don’t need projection, agregation, etc.
Do you think you can extract that in some core
bundle and deliver it separetely (at least its ES6 version)?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:13 (13 by maintainers)
Top Results From Across the Web
operator overloading - cppreference.com
[edit] Overloaded operators. When an operator appears in an expression, and at least one of its operands has a class type or an...
Read more >Functions and Operators | User Guide | Support | Epi Info - CDC
Boolean Operators include AND, OR, XOR, or NOT and can have one of two values, true or false. Operator Precedence. If several operations...
Read more >Operator Overloading, C++ FAQ - Standard C++
In general, your operator should change its operand(s) if and only if the operands get changed when you apply the same operator to...
Read more >Nullish coalescing operator (??) - JavaScript - MDN Web Docs
The nullish coalescing (??) operator is a logical operator that returns its right-hand side operand when its left-hand side operand is null ...
Read more >Logical operators - The Modern JavaScript Tutorial
There are four logical operators in JavaScript: || (OR), && (AND), ! (NOT), ?? (Nullish Coalescing). Here we cover the first three, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey @stalniy, thanks for creating this issue.
I agree with you that this should perhaps be split across different modules.
That has been my plan from the start which gave birth to mingo-geo and mingo-stream packages even though they haven’t seem much development since.
I think why I didn’t pursue this fully was that the operators weren’t that many at the time and the convenience of hosting everything in one package.
I will explore how best this can be split up by functionality into separate packages and while keeping them amalgamated in this one by taking dependencies (e.g.
mingo-core
,mingo-aggregate
etc). It could be more challenging than I anticipate given I that I have implemented some operators by depending on others which might end up being separated.You are welcome to share any ideas about this.
Thanks.
The coming
3.0.0
loads only query and projection operators by default. All other operators must be explicitly required and registered. This effectively supports tree shaking to reduce bundle size.