Colorize SQL colors code incorrectly if there's any multi-line comment which is opened and closed in the same line

[rdomene]

Describe the bug
Colorize SQL colors incorrectly when there are multi-line comments that are opened and closed in the same line. It colorizes as a comment all the lines between the first "/" string and the last "/" string that does not have another "/*" in the same line.

To Reproduce
Steps to reproduce the behavior:

1. Go to any page.
2. Paste the following SQL code:

SELECT
	GETDATE() AS [Today],
	/* This is a multi-line comment that starts and ends in the same line */
	(GETDATE() + 1) AS [Tomorrow],
	CAST(1 as bit) AS [Boolean],
	/*This is another multi-line comment that starts and ends in the same line */
	CAST(1 as int) AS [Number]
GO

/*
** SQL 2
*/

SELECT
	GETDATE() AS [Today],
	/* This is a multi-line comment that starts and ends in the same line */
	(GETDATE() + 1) AS [Tomorrow],
	CAST(1 as bit) AS [Boolean],
	/*
	This is a multi-line comment that starts and ends in different lines
	*/
	CAST(1 as int) AS [Number]
GO

3. Select all the code.
4. Click on More > Colorize > SQL
5. Color pattern is incorrect as some non-comment lines are colorized as comments.

Expected behavior

Right color pattern should be similar to this one:

Obtained color pattern is this one:

Environment (if applicable):

• Microsoft® OneNote® 2016 MSO (version 2208 compilation 16.0.15601.20148) - 64 bits
• OneMore Version 5.1.0

[stevencohn]

This should be fixed in 5.1.0 and in fact, I cannot reproduce this given the text that you provided.

[rdomene]

Interesting.

I uninstalled and reinstalled OneMore, just in case.

Then I copied and pasted the SQL code I pasted as a sample. Just Copy & Paste. I selected the text, then clicked Colorize > SQL, and the text was properly colored.

But... after that, I copied the code and pasted it with the Paste Special > Paste Keep Text Only option (this is the method I use most of the time), and then I select the text, click Colorize > SQL, then the coloring pattern is incorrect.

[stevencohn]

That's helpful. Thanks. Looking into it