Wrong Tabstop-index with inserted nested snippets

[JohnnyCrazy]

Test-Case:

var suggestions = [];
suggestions.push({
    snippet: "TestMethodOne(${1:position})${2}",
});
suggestions.push({
    snippet: "Vector(${1:x}, ${2:y}, ${3:z})${4}",
});
return resolve(suggestions)

Result:

Expected:
After you inserted some text for the x-Variable, the next TAB should lead to the y-Variable but instead it goes to the end of the outer function. The next tabstop-index should always consider last inserted snippets before other ones IMO. This makes working with nested snippets nearly impossible.

I tried pasting both snippets into the snippets.cson and got inverted results ( covered in atom/snippets#152), so I opened the issue here since it propably is related to AC+ somehow.

[steelbrain]

👍

[benogle]

This is probably a snippets issue, not an autocomplete-plus issue

[JohnnyCrazy]

I tried pasting both snippets into the snippets.cson and got inverted results ( covered in atom/snippets#152), so I opened the issue here since it propably is related to AC+ somehow.

@benogle

To be clear: Pasting both snippets into the snippets.cson will not reproduce this bug