Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent node name collisions when drag-and-dropping multiple files #10979

Merged
merged 4 commits into from
Sep 5, 2024

Conversation

Frizi
Copy link
Contributor

@Frizi Frizi commented Sep 4, 2024

Fixes #10961

Important Notes

Fixed a few warnings in dashboard caused by missing or misplaced key attributes.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

  • The documentation has been updated, if necessary.
  • Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
  • All code follows the
    Scala,
    Java,
    TypeScript,
    and
    Rust
    style guides. In case you are using a language not listed above, follow the Rust style guide.
  • Unit tests have been written where possible.

Copy link
Contributor

@somebody1234 somebody1234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approving dashboard changes

delayedNodesToCreate.push(options)
// Delay node creation to next tick, batch multiple synchronous createNode calls together
// to avoid node name collisions.
if (delayedNodesToCreate.length === 1) {
Copy link
Contributor

@vitvakatu vitvakatu Sep 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A strict === 1 comparison seems suspicious, why not >= 1? It kinda contradicts the comment which says batch multiple … calls together

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It schedules a flush operation when the queue transitions from empty to non-empty. If the queue is already non-empty (i.e. after adding an element, the queue's new length is 2 or more), a flush has already been scheduled.

@Frizi Frizi added the CI: Ready to merge This PR is eligible for automatic merge label Sep 5, 2024
@mergify mergify bot merged commit cab161a into develop Sep 5, 2024
33 of 34 checks passed
@mergify mergify bot deleted the wip/frizi/drop-multifile-node-names branch September 5, 2024 12:27
somebody1234 pushed a commit that referenced this pull request Sep 8, 2024
…10979)

# Important Notes
Fixed a few warnings in dashboard caused by missing or misplaced key attributes.
jdunkerley pushed a commit that referenced this pull request Sep 9, 2024
…10979)

# Important Notes
Fixed a few warnings in dashboard caused by missing or misplaced key attributes.

(cherry picked from commit cab161a)
jdunkerley pushed a commit that referenced this pull request Sep 10, 2024
…10979)

# Important Notes
Fixed a few warnings in dashboard caused by missing or misplaced key attributes.

(cherry picked from commit cab161a)
jdunkerley pushed a commit that referenced this pull request Sep 10, 2024
…10979)

# Important Notes
Fixed a few warnings in dashboard caused by missing or misplaced key attributes.

(cherry picked from commit cab161a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dragging two files on to the graph editor at the same time results in the same variable name
4 participants