Waypoint callout is Bugged

[AlyceOsbourne]

When nesting a waypoint inside a callout, it causes the callout to not be cleared before being updated properly.

Before a file is added it looks like this

After

I am not sure the code the detects the contents of the waypoint takes into account the >

[ltchin]

I think I found the issue. In lines 234-243 of main.ts

if (waypointStart === -1 && (trimmed.includes(waypointFlag) || trimmed.includes(beginWaypoint))) {
	isCallout = trimmed.startsWith(">");
	initialWaypoint = trimmed.includes(waypointFlag);
	waypointStart = i;
	continue;
}
if (waypointStart !== -1 && trimmed === endWaypoint) {
	waypointEnd = i;
	break;
}

There should be a line to change endWaypoint to have a > marker in front as well. Probably before the continue; . I'm pretty sure waypointEnd just stays as -1, which is why it would overshoot.

I do not have a Typescript dev environment though, so I can not test if the fix works. Would appreciate if someone could try it and see if that fixes it.

[j-adel]

I really hope someone can make a built out of @ltchin 's suggestion. Callouts are a must have for me to use this plugin, unfortunately :/