Fixes #38260 - Unregister duplicate event listeners for select2 #11329
+2
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What are the changes introduced in this pull request?
Some event listeners get registered multiple times, causing unnecessary calls. This change tries to make sure one of the event listeners gets registered once.
Considerations taken when implementing this change?
Easiest solution?.. Probably fixes only described issue.
What are the testing steps for this pull request?
Actual behavior:
The lifecycle environment select offers the same environments many times, depending on how many times the organization was changed in step 3.
Expected behavior:
Each environment is offered only once
@MariaAga, you might want to check this.