There were several cases where the automatic semicolon insertion for devicetree files did not work correctly:
- It did not check for existing semicolons, and would always insert another if a closing bracket was added.
- It inserted the semicolon at the end of the replaced range instead of the end of the inserted range. This would put semicolons in the middle of the insertion if the new text was longer than the old.
Both of these issues are now fixed.