# Coming in 8.1.18: Script editor improvements

**URL:** <https://forum.inductiveautomation.com/t/coming-in-8-1-18-script-editor-improvements/59629>\
**Category:** Ignition\
**Created:** [May 16, 2022, 6:39pm UTC](https://forum.inductiveautomation.com/t/coming-in-8-1-18-script-editor-improvements/59629 "2022-05-16T18:39:17Z")\
**Posts on this page:** 1\
**Showing post:** 36

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 23, 2022, 6:17pm UTC](https://forum.inductiveautomation.com/t/coming-in-8-1-18-script-editor-improvements/59629/36 "2022-06-23T18:17:31Z")

</div>

Thanks to @bschroeder and @mazeyrat for sending in samples (and @bschroeder for noticing the crucial insight) - the issue with parsing is with continuation lines/expressions wrapped to multiple lines. I’m going to do my best to work around it (ideally for 8.1.19) but for now, avoid patterns like this:

```python
for key in ["abc-%s" % site,
			"def-%s" % site,
			"ghi-%s" % site]:

```

Or other continuations with mixed indentation:

```python
def abc2():
	doSomething(
			a,
		)
	

```

---

_[View the full topic](https://forum.inductiveautomation.com/t/coming-in-8-1-18-script-editor-improvements/59629)._