Closed vjekob closed 2 years ago
When Ninja is configured to suggest object IDs per range (objectIdNinja.requestPerRange configuration setting) and there are multiple ranges, then suggestions are not sorted correctly.
objectIdNinja.requestPerRange
For example, ranges are configured like this:
[ { "from": 50000, "to": 99999, }, { "from": 2150500, "to": 2150599 } ]
Ninja will suggest these IDs (in this order):
2150500 50000
Suggestions should be sorted like this:
50000 2150500
The sort order should not be numeric, but should follow the range order in app.json.
app.json
Closed with 2.4.1
When Ninja is configured to suggest object IDs per range (
objectIdNinja.requestPerRange
configuration setting) and there are multiple ranges, then suggestions are not sorted correctly.For example, ranges are configured like this:
Ninja will suggest these IDs (in this order):
Suggestions should be sorted like this:
The sort order should not be numeric, but should follow the range order in
app.json
.