updated changelog for v0.3.0.0

Author: unclechu

.editorconfig

@@ -9,6 +9,9 @@ end_of_line = lf
 indent_style = space
 indent_size = 2
 
+[*.md]
+trim_trailing_whitespace = false
+
 [test/**.hs]
 trim_trailing_whitespace = false
 

CHANGELOG.md

@@ -1,12 +1,32 @@
 ## <a name="v0.3.0.0"></a>0.3.0.0
 
 * Testing on GHC 8.2.2
+* More tests to cover more usage scenarios
+* Ability to use `}` inside an interpolation block by escaping it
 
 ### **WARNING!** Breaking changes
 
-* TODO explain better: Breaking change of interpolation blocks
-* TODO explain better: Quoters no longer removes every *CR* (`\r`), but just
-    supports *CRLF* (`\r\n`) line-breaks
+* `\r` characters are no longer pre-removed.
+
+  Up to [v0.2.1.0](#v0.2.1.0) all `\r` characters were pre-removed. When you
+  compile your code with GHC you can use either *LF* or *CRLF* for line-breaks
+  but not *CR* alone. When I changed handling of interpolation blocks (see
+  below) I needed to get contents of interpolations blocks without **any**
+  modifications, so I replaced pre-removing all *CR*s with explicit handling of
+  *CRLF* in patterns. If your code ever was depending on `\r` symbols appearing
+  alone inside quoters (that I can't even imagine) it could break your code.
+  But it will probably never happen, I'm just noticing it here.
+
+* Fix for interpolation blocks parsing.
+
+  Once I noticed that `[qm|{"\n"}|]` compiles to `"n"`, I considered this as a
+  bug, I also realized that interpolation blocks aren't interpreted as a bare
+  haskell code as I was expecting. My bad, I've missed that, haven't written
+  enought tests to cover such scenarios, it migrated from original
+  *interpolatedstring-perl6* package. So I had to fix this mistake,
+  notwithstanding it can break your code when you update the library. Now
+  everything inside interpolation blocks is taken as bare haskell code as
+  possible.
 
 ## <a name="v0.2.1.0"></a>0.2.1.0