Add unique ID generation for TreeNodeInfo and corresponding tests #19481
+43
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Template – vscode-mssql
Description
This PR fixes #19479
Previously when creating nodes in quick succession,
Data.now()
was returning the same millisecond value causing conflicts if 2 items have the same label under the same parent. using performance.now() is also a valid solution but, I am switching to guid as we don't need time specific information in the id as of now.Code Changes Checklist
npm run test
)Reviewers: Please read our reviewer guidelines