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
Copy file name to clipboardExpand all lines: Docs/readme/advantages.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
-
## 🤩 Advantages
1
+
## 🤩 Advantages<aname="advantages"/>
2
2
3
3
1.**Friendliness**
4
4
5
5
JSON is a simple and widely known format, easy to read not only for developers.
6
6
7
7
1.**Broad applicability**
8
8
9
-
JSON-based filters can be used in tests, described in specifications, test plans, and other technical documentation, lowering the entry barrier for readers.
9
+
JSON-based filters can be used in tests, specifications, test plans, and other technical documentation, lowering the entry barrier for readers.
10
10
11
11
1.**Universality**
12
12
@@ -22,13 +22,13 @@
22
22
23
23
1.**Simplicity**
24
24
25
-
Install the NuGet package and pass JSON filters into `Where()` and other LINQ methods. This enables not a minimal subset, but the full filtering functionality.
25
+
Install the NuGet package and pass JSON filters into `Where()` and other filtering methods. This enables not a minimal subset, but the full functionality.
26
26
27
27
**No need to:**
28
28
29
-
- Register anything in `Program.cs`
30
-
- Create schemas, separate DTOs, filters, resolvers, etc.
31
-
- Generate a schema for the client
29
+
- Register anything in `Program.cs`.
30
+
- Create schemas, framework-specific DTOs, filters, resolvers, etc.
31
+
- Generate a schema for the client.
32
32
33
33
Everything required for filtering is already contained in the DTOs.
0 commit comments