You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`enableRegex` has been removed and replaced with `MATCHES` filters in the features configuration object. See the migration guide for more information: https://neo4j.com/docs/graphql-manual/current/guides/v4-migration
Copy file name to clipboardExpand all lines: docs/modules/ROOT/pages/filtering.adoc
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,9 +127,6 @@ const features = {
127
127
const neoSchema = new Neo4jGraphQL({ features, typeDefs, driver });
128
128
----
129
129
130
-
131
-
Previously to enable to this filter the config option `enableRegex` was used, it has been deprecated. Use the `features` configuration object as described here, as the `enableRegex` will be removed in the future.
132
-
133
130
> The nature of RegEx matching means that on an unprotected API, this could potentially be used to execute a ReDoS attack (https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) against the backing Neo4j database.
Copy file name to clipboardExpand all lines: docs/modules/ROOT/pages/guides/v4-migration/index.adoc
+23-1Lines changed: 23 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,29 @@ npm update @neo4j/graphql
19
19
If you were passing any arguments from https://the-guild.dev/graphql/tools/docs/api/interfaces/schema_src.iexecutableschemadefinition[`IExecutableSchemaDefinition`] into the library
20
20
other than `typeDefs` and `resolvers`, these are no longer supported.
21
21
22
+
=== config.enableRegex replaced by `MATCHES` in features.filters
23
+
24
+
`config.enableRegex` has been replaced by `MATCHES` in features.filters. With this change comes more granularity in the feature configuration. You can now enable the `MATCHES` filter on `String` and `ID` fields separately.
25
+
26
+
A direct replacement of the `enableRegex: true` configuration would be as follows:
27
+
28
+
[source, javascript, indent=0]
29
+
----
30
+
neoSchema = new Neo4jGraphQL({
31
+
typeDefs,
32
+
features: {
33
+
filters: {
34
+
String: {
35
+
MATCHES: true,
36
+
},
37
+
ID: {
38
+
MATCHES: true,
39
+
},
40
+
},
41
+
},
42
+
});
43
+
----
44
+
22
45
== Updated Directives
23
46
24
47
We have renamed a number of directives and their arguments, in order to make using `@neo4j/graphql` more intuitive.
@@ -577,7 +600,6 @@ const neoSchema = new Neo4jGraphQL({
0 commit comments