[CLOSED] More CSS parsing unit tests (and beef up EditorManager docs)

[core-ai-bot]

Issue by peterflynn
Thursday Mar 01, 2012 at 19:06 GMT
Originally opened as adobe/brackets#358

---

• Add "known issue" unit tests for [CLOSED] Inline editor includes comment after rule #338 and [CLOSED] Exception when IP is between '=' and double-quote and pressing Cmd+E #343, and add another case to the test for [CLOSED] Quick file open #332
• Document EditorManager.createInlineEditorFromText() better; in particular, the semantics of range

---

peterflynn included the following code: https://github.com/adobe/brackets/pull/358/commits

[core-ai-bot]

Comment by chrisbank
Thursday Mar 01, 2012 at 19:22 GMT

---

reviewing

[core-ai-bot]

Comment by chrisbank
Thursday Mar 01, 2012 at 19:43 GMT

---

@peterflynn looks good. Just fix the lint errors on that line.

[core-ai-bot]

Comment by peterflynn
Thursday Mar 01, 2012 at 20:02 GMT

---

I fixed the JSLint errors and added more !/? to that comment.
I also realized the docs for expectParseError()'s 2nd arg were totally wrong (doh!), so I fixed that.
Finally, I added a few more cases to cover additional parsing errors Randy mentioned in issue #343.

[core-ai-bot]

Comment by chrisbank
Thursday Mar 01, 2012 at 22:10 GMT

---

looks good