Research
Security News
Malicious npm Package Targets Solana Developers and Hijacks Funds
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
io.github.habeebcycle:o-data-query-builder
Advanced tools
An eloquently fluent OData query builder for Java Client.
OData Query Builder in Java for Java Applications v 0.0.4
Inspired by Jared Mahan An eloquently fluent OData query builder for NPM
Use Maven
<dependencies>
<dependency>
<groupId>io.github.habeebcycle</groupId>
<artifactId>o-data-query-builder</artifactId>
<version>0.0.4</version>
</dependency>
...
</dependencies>
or Gradle
implementation group: 'io.github.habeebcycle', name: 'o-data-query-builder', version: '0.0.4'
or
implementation 'io.github.habeebcycle:o-data-query-builder:0.0.4'
String query = new QueryBuilder()
.count()
.top(5)
.skip(5)
.expand("MyProps")
.orderBy("MyProp2")
.filter(f -> f.filterExpression("Property", EQ, "MyValue"))
.select("Field1,Field2")
.toQuery();
Outputs:
?$orderby=MyProp2&$top=5&$skip=5&$count=true&$expand=MyProps&$select=Field1,Field2&$filter=Property eq 'MyValue'
Filter expressions utilize logical operators to filter data on a specific property.
Operator Options, changed in version 0.0.2 and above:
eq
- FilterExpression.EQ
ne
- FilterExpression.NE
gt
- FilterExpression.GT
ge
- FilterExpression.GE
lt
- FilterExpression.LT
le
- FilterExpression.LE
Operator Options, version 0.0.1:
eq
- FilterExpression.EQUALS
ne
- FilterExpression.NOT_EQUALS
gt
- FilterExpression.GREATER_THAN
ge
- FilterExpression.GREATER_THAN_EQUAL
lt
- FilterExpression.LESS_THAN
le
- FilterExpression.LESS_THAN_EQUAL
String query = new QueryBuilder()
.filter(f -> f.filterExpression("Property1", EQ, "Value1"))
.toQuery();
Outputs: ?$filter=Property1 eq 'Value1'
You can also combine filter expressions in version 0.0.2 and above:
String[] values = {"value1", "value2"}; // or you can pass a list: List.of("value1", "value2")
String query = new QueryBuilder()
.filter(f -> f.filterExpressions("Property1", FilterExpression.EQ, values)).toQuery();
Outputs: ?$filter=Property1 eq 'value1' and Property1 eq 'value2'
Filter phrases are to be used with canonical functions. Filter Phrasing exposes the filter as a string which allows you to inject any of the various filtering mechanisms available in OData v4
.
Below are a few examples:
String query = new QueryBuilder()
.filter(f ->
f.filterPhrase(FilterPhrases.contains("Property1","Value1"))
.filterPhrase(FilterPhrases.startsWith("Property1","Value1"))
.filterPhrase(FilterPhrases.endsWith("Property1","Value1"))
.filterPhrase(FilterPhrases.indexOf("Property1","Value1", EQ, 1))
.filterPhrase(FilterPhrases.length("Property1", EQ, 19))
.filterPhrase(FilterPhrases.substring("Property1", 1, 2, EQ, "ab"))
).toQuery();
Outputs: ?$filter=contains(Property1,'Value1') and startswith(Property1,'Value1') and endswith(Property1,'Value1') and indexof(Property1,'Value1') eq 1 and length(Property1) eq 19 and substring(Property1, 1, 2) eq 'ab'
You can also combine filter phrases in version 0.0.2 and above:
List<String> phrases = List.of("startswith(Property1,'Value1')", "contains(Property1,'Value1')", "length(Property1) eq 19"); //you can also pass an array new String[]{"startswith(Property1,'Value1')", "length(Property1) eq 19"}
String query = new QueryBuilder()
.filter(f -> f.filterPhrases(phrases)).toQuery();
Outputs: ?$filter=startswith(Property1,'Value1') and contains(Property1,'Value1') and length(Property1) eq 19
By default, when you utilize .filter
you are using the and
operator. You can be explicit by passing your operator into the filter as a secondary parameter.
String query = new QueryBuilder().filter(f -> f
.filterExpression("Property1", EQ, "Value1")
.filterExpression("Property2", EQ, "Value1"),
AND)
.toQuery();
Outputs: ?$filter=Property1 eq 'Value1' and Property2 eq 'Value1'
String query = new QueryBuilder()
.filter(f -> f
.filterExpression("Property1", EQ, "Value1")
.filterExpression("Property2", EQ, "Value2"),
AND)
.toQuery();
Outputs: ?$filter=Property1 eq 'Value1' and Property2 eq 'Value2'
String query = new QueryBuilder()
.filter(f -> f
.filterExpression("Property1", EQ, "Value1")
.filterExpression("Property2", EQ, "Value2"),
OR)
.toQuery();
Outputs: ?$filter=Property1 eq 'Value1' or Property2 eq 'Value2'
Nested or grouped filtering is used when we need to write a more complex filter for a data set. This can be done by utilizing .and()
or .or()
with the filter.
String query = new QueryBuilder()
.filter(f -> f
.filterExpression("Property1", EQ, "Value1")
.filterExpression("Property2", EQ, "Value2")
.and(f1 -> f1 //can be - 'or'
.filterExpression("Property3", EQ, "Value3")
.filterExpression("Property4", EQ, "Value4")
)
)
.toQuery();
Outputs: ?$filter=Property1 eq 'Value1' and Property2 eq 'Value2' and (Property3 eq 'Value3' and Property4 eq 'Value4')
String query = new QueryBuilder()
.filter(f -> f
.filterExpression("Property1", EQ, "Value1")
.filterExpression("Property2", EQ, "Value2")
.or(f1 -> f1 //can be - 'and'
.filterExpression("Property3", EQ, "Value3")
.filterExpression("Property4", EQ, "Value4")
)
)
.toQuery();
Outputs: ?$filter=Property1 eq 'Value1' and Property2 eq 'Value2' and (Property3 eq 'Value3' or Property4 eq 'Value4')
String query6 = new QueryBuilder()
.filter(f -> f
.filterExpression("Property1", EQ, "Value1")
.filterExpression("Property2", EQ, "Value2")
.and(f1 -> f1 //can be - 'or'
.filterExpression("Property3", EQ, "Value3")
.filterExpression("Property4", EQ, "Value4")
),
AND //can be - "or"
)
.toQuery();
Outputs: ?$filter=Property1 eq 'Value1' and Property2 eq 'Value2' and (Property3 eq 'Value3' or Property4 eq 'Value4')
FAQs
An eloquently fluent OData query builder for Java Client.
We found that io.github.habeebcycle:o-data-query-builder demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.