We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 658217b commit c1c631eCopy full SHA for c1c631e
changelog.d/1569
@@ -0,0 +1,13 @@
1
+synopsis: Encode captures using toEncodedUrlPiece
2
+prs: #1569
3
+issues: #1511
4
+
5
+description: {
6
+The `servant-client` library now makes direct use of `toEncodedUrlPiece` from `ToHttpApiData`
7
+to encode captured values when building the request path. It gives user freedom to implement
8
+URL-encoding however they need.
9
10
+Previous behavior was to use `toUrlPiece` and URL-encode its output using `toEncodedUrlPiece`
11
+from the `Text` instance of `ToHttpApiData`. The issue with this approach is that
12
+`ToHttpApiData Text` is overly zealous and also encodes characters, such as `*`, which are perfectly valid in a URL.
13
+}
0 commit comments