Fix GroupDecree tokenizer bug

When we were processing a nested closing decree, we were forgetting to
add it to the current clause, thus causing confusion when someone later
tried to parse that clause and missed their ending token.

1 files changed, 2 insertions, 0 deletions

diff --git a/clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java b/clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java
index d2ccfd2..1b9c90f 100644
--- a/clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java
+++ b/clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java
@@ -231,6 +231,8 @@ public class CLTokenizer implements Iterator<Decree> {
 			} else if (curDecree.isNamed(desiredClosing)) {
 				// Unnest
 				nestingLevel -= 1;
+
+				curClause.addChild(curDecree);
 			} else {
 				curClause.addChild(curDecree);
 			}